Re: Just found php.ini has a 90M limit

Post #336,608 by folkert 12/3/10 9:42:02 AM Reply	Re: Just found php.ini has a 90M limit StartServers 2 MinSpareServers 2 MaxSpareServers 5 MaxClients 7 <---- that one MaxRequestsPerChild 1000 Of course I'm oblivious to what might happen... people will wait. FYI, I already see a significant wait time to have your site render. I'm not so sure you want to limit the number of instances...
Post #336,614 by drook 12/3/10 9:53:21 AM Reply	Noticed that recently too What's odd is that when it does come up, it comes up all at once. Is there a directive that instructs the browser not to render until all the images are downloaded? -- Drew
Post #336,618 by jake123 12/3/10 10:57:20 AM Reply	That can happen if your software isn't providing the image dimensions to the browser....
Post #336,630 by drook 12/3/10 1:26:21 PM Reply	But it is ... I already made sure of that ... oh wait Sonofabitch. Several sidebar widgets didn't have their dimensions listed. Ehh ... just fixed them all and it still waits until everything is there to render. Firebug is showing 3-7 seconds for the initial page get. That blows. -- Drew
Post #336,636 by malraux 12/3/10 3:33:17 PM Reply	CSS listed first on the page? And Javascript should be last, after the content. CSS is required to properly render, and the Javascript will single-thread and cause everything to wait while it is being retrieved. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #336,649 by drook 12/3/10 5:09:15 PM Reply	Don't think that's the problem That 3-7 second delay I mentioned is on the first page load. Nothing else starts downloading until after that. -- Drew
Post #336,653 by malraux 12/3/10 5:35:50 PM Reply	Have you tried FireBug's Net tab or IEWatch? Something that tells you what is loading when, and how long it takes. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #336,660 by drook 12/3/10 7:34:10 PM Reply	That's where I get the 3-7 seconds for initial page load -- Drew
Post #336,705 by scoenye 12/4/10 3:25:07 PM Reply	No long delay here + a couple of observations The redirect from www.cooklikeyourgrandmother.com to cooklikeyourgrandmother.com adds almost a second to the initial page load time in my case. It also generates a second DNS hit. If your DNS server is slow to resond or you have a broken forwarder (say a certain type of Belkin wireless router) this could easily exacerbate the delay. There are no long delays downloading parts once the root page is loaded. I do see long delays closing connections, but that does not seem to have an effect on page display. The delays occur on both sides, so this may just be the way HTTP works. E.g. the last request is finished after 9s but the last connection is closed at 22s. The blog doesn't have the redirect overhead and otherwise behaves the same as the main page. Most of the static content you provide (images, css, ...) has the Expires header set to April 15 2010. This sets up an extra trip to the server for everything that is used more than once.
Post #336,711 by drook 12/4/10 5:33:10 PM Reply	Thanks for noticing the expires header The article I copied some optimization tips from was written in 2007. At the time 2010 was "far future". -- Drew

Welcome to IWETHEY!