[PROBLEM] TS 209 Pro painfully slow with SQL sites

[Magistic]

Hi there,

First of all I want to say that I absolutely LOVE my Qnap!

The only problem I encountered with it is that all SQL driven websites are painfully slow on my 209 Pro.
And with SQL driven websites I mean Wordpress, Joomla, Drupal etc.

I configured my apache.conf to have Virtual Hosts.

The following code is on the end of my apache.conf

Code: Select all

NameVirtualHost *

<VirtualHost *>
   DocumentRoot "/share/Qweb"
</VirtualHost>

<VirtualHost *>
ServerName marcoblomsma.nl
ServerAlias www.marcoblomsma.nl
DocumentRoot "/share/Qweb/marco"
</VirtualHost>

<VirtualHost *>
ServerName wimblomsma.nl
ServerAlias www.wimblomsma.nl
DocumentRoot "/share/Qweb/wim"
</VirtualHost>

This works fine when I host a static website full of pictures, text and video's, it just loads instantly...
But as soon as I try Wordpress, or any other SQL driven site, it takes a good 10 seconds to load the page.

Example static website:
http://www.wimblomsma.nl

Example SQL website:
http://www.marcoblomsma.nl/drupal
http://www.marcoblomsma.nl/wordpress

What could be wrong?

[texc4]

I have also the same problem, does anyone have an idea ?

[Magistic]

No one else with problems, or no one with a solution?

[Don]

The 209 pro is running a 500mhz Marvell arm processor with 128mb of memory. It is not going to be fast at anything.

[BoNz]

It seems this is a recurrent problem on Joomla 1.5, and ARM based devices. It seems there's no such problem with Joomla! 1.0 (!).

I had the same issue with a TS 109 II, tried installing the CMS on lighttpd, but it was still slow. As I didn't really figure how to install Joomla 1.5 on SQLlite, I tried putting the latest version of Wordpress, to see,and it worked fast enough to be used.

After digging on the net, I found that some users of similar hardware from different brands had the same speeds problems and advised to use the version 1.0 instead of the 1.5. I tried and it worked quite fast with some content and modules enabled

I am looking forward to hear if other users at the same experiences and what was there solution (if any).