Thread

This site (http://www.will-co.nl/index.php build with EE 1.7.0) loads extremely slow. Also the CP. I do not know what to do. PHP memory limit=8M.  PHP Version 4.4.9 It seems as if the server hesitates. I tried already Generate HTTP Page Headers off, no difference. When I switch debugging on, the page loads: 2.132783 Template Parsing Finished and uses Memory Usage: 2,526,480 bytes.
Force URL query strings is on, because the server needs the questionmark after php.

I do hope someone helps me here, because my client will not like this.

atelier2,

Your PHP memory is very low. Most hosts these days have a default of at least 64MB to 128MB

Can you try upping that please?

FYI the front end loads quite fast for me. Is this specific to the CP?

Do you have any extensions installed?

Hi, thanks. I’ll contact the ISP of my client.
No extentions yet, I just started building.
Strange that you noticed a fast load of the frontend index. Here the server ‘hesitates’ before anything happens. Also the CP is slow. It’s not my connectionspeed, that is avarage :
Download 6.94 Mb/s Up 0.73 Mb/s Ping 45 ms.

ateilier2, the front end of the site loads fairly quickly for me as well. It may be your location..

Let us know if getting more PHP memory helps, We’ll be here.

Hi

I called with the ISP of the client, they generously increased the memory to a whopping 32 Mb.

Very strange that it could be my location. Other sites runn as usual.
....I had to wait for 55 sec just to log in, and call something like templates…....

But if there is nothing I can do in my build, maybe we close the case? Thanks a lot for assisting!

Hi atelier2,

If you switch on template debugging and the display of SQL queries you should be able to see whether any particular module/plugin or query is taking a rather long time or whether there is a reasonably consistent time across all the calls to generate your template. Make sure that you are using the weblog:entries disable parameter whenever you can.

Cheers

Greg

Try adding some DNS servers to your network settings on your computer - like googles
8.8.8.8
8.8.4.4

The hesitation could be your DNS settings on your computer or router which are often automatically set by your ISP.
(front page loaded quick from here - eastern US)

Hi atelier2,
Make sure that you are using the weblog:entries disable parameter whenever you can.

Cheers

Greg

Thanks Greg. II’ll look at the debugging output.
About the disable parameter, I have a habit to use the disable parameter as much as possible.

Try adding some DNS servers to your network settings on your computer - like googles
8.8.8.8
8.8.4.4

The hesitation could be your DNS settings on your computer or router which are often automatically set by your ISP.
(front page loaded quick from here - eastern US)

Thanks handyman

The frontend you see now is the off-line template. But even that one -sometimes!- hesitates and loads slow here. Except for yesterday evening, late, then the site responded quickly. All other sites, all my other EE builds run normal, BTW.  I’ll look at adding DNS servers. But strange that it’s just this one build.
Anyway, I’m almost finished here, now the testteam wil ljoin from other places, we’ll see if just this server keeps being slow.

wow, upped you to 32mb?

i would demand a minimum of 64mb, and if they can’t do it, there are so many hosts that will.

i know that once i added a few cool extensions, especially ones that do something like resize an image on upload, low ram caused “white screens of death”. 32mb won’t cut it for long.

😊

I know, they’re rather greedy there. It was not my choice, this ISP.
Actually i do think the slow site access is due to that low memory.
Today (sunday here) I could work ‘as normal’ on the site, meaning not so much traffic.

atelier2, unfortunately you may need to have a frank talk with the client about moving servers. But there are some things you can do to help, such as using the disable= parameter, turning off stats, that sort of thing.

thanks for helping. I talked already with he client, do it will be solved inthe future.

Sounds good. Please let us know if there’s anything else we can do for you.