globetrotter wrote:When I change something on my site, it takes a long time before I can see the results.
First of all, let me explain that this is how X3 works ... When you "change" anything in your X3 website, it invalidates the cached pages. The next time you visit any page, it needs to re-process all data again, including the relatively heavy menu. Therefore, it will always be "slower" after you make changes, but will speed up once pages and templates get cached.
When your page is "cached", it is OK fast:
http://tools.pingdom.com/fpt/#!/b79toJ/ ... ternet.nl/
(The main html document loads in after 1.5 seconds wait)
globetrotter wrote:The site will not load most of the times.
Yes I experienced this today also. I really don't like to blame hosting services when an X3 website fails to load, but your hosting service is simply under-powered, or more likely "over-shared". Your website didn't have a huge amount of folders, and it still doesn't manage to process them. To be honest, I have posted it earlier also, you would need to be very lucky if you are hosting on a 3$ service and they offer sufficient resources. I don't even understand their pricing:You are on the "professional" package, which is more GB (ok), but how do they quantify "2x CPU" I wonder, when it is shared between 1000s of users ...
globetrotter wrote:Sometimes I have to wait for 15 minutes, several hours or even untill the next day. I try to refresh the page every 5 minutes or so.
Your website has a 60-second timeout, so it simply times out. The only reason it maybe works the next day, is perhaps because your page was accessed once at some time when there are less visitors on your over-shared hosting service.
globetrotter wrote:Also 'Create Menu' does not work always. Most of the times I see the error: 503 Service Unavailable.
Other moments it is ready in a few seconds. Then the site will load OK.
The create-menu is proportional with the general site timeout, because it is the most heavy process. When it loads quickly, it's likely because the menu-fragment is already cached.
globetrotter wrote:But most of the times I have the same problems.
Maybe my webspace host is not fast enough or it is to busy on internet sometimes? Or some configuration mistakes?
Unfortunately, it is the hosting. You could try the open_basedir-fix as suggested by @Scoop643, but personally I can't see any logical reason that would speed things up dramatically.
Suggestions
- First of all, the speed (and failure) is directly related to the amount of folders and files in your content structure. Try to
RENAME the sample "3.examples" folder to "_examples" which an underscore before the name. This should prevent it from being taken into account when the system is looping through folders. Avoid unnecessary folders/content.
- Change host. This is the ultimate fix beyond doubt. This host may work until you get to a certain amount of files and images, but that's it.
- I Checked the host again ... I really don't see how they quantify their resources provided, but their naming is inappropriate. It would only be logical to guess that the two bottom packages are for really light static websites ... They really don't offer much resources. You could try next package up, although even they are considered "cheap", and I really don't know how much better they will perform on this host.
- After things are "working", you can fortify your website by using cloudflare. (see
post here)