
pablosaro at gmail
Jun 19, 2009, 4:50 PM
Post #4 of 7
(844 views)
Permalink
|
Hi Jason, Regarding the Zend cart (BTW I've never used it) I think it is not a good idea to fill a combo box with data in a MySQL table for about 30K rows (and the possibility of becoming larger). Just think about MySQL times and PHP times... Ugh... Why not having that list cached somewhere and perform a search over the cache? I don't know if it is possible with Zend cart. Sorry if it is out of list's scope. Pablo On 6/19/09, Jason <superman.jason [at] gmail> wrote: > Alvaro Lopez Ortega <alvaro <at> alobbs.com> writes: > >> >> Hello Jason, >> >> On 18-jun-09, at 19:47, Jason wrote: >> >> > While I've got the experts at work I'd like to request a little more >> > help if I >> > could. >> > >> > I find cherokee processes php files very quickly most of the time. >> > The only >> > times I run into problems is when there's a time delay in processing >> > an action. >> > >> > For example, the php gallery I've been using (Singapore - >> > http://sgal.org/ >> > - old >> > but still works well!) works fine except when I add new images. The >> > script >> > processes the added files and creates & caches the newly resized >> > images for >> > thumbnails, page display etc. When this is taking place if the image >> > is large, >> > or there are several images to process I'll often get a 504 gateway >> > timeout, or >> > a 500 server error message. If I keep refreshing eventually I'll get >> > back to the >> > page. I'm guessing this is because cherokee times out when waiting >> > for a >> > response from php-cgi or something like that. >> >> Yes, it looks like it. Cherokee closes the connection if php doesn't >> return any information within the server-wide timeout limit. >> >> The second option would be that all your php-cgi child processes were >> busy running 'gd' or 'imagemagick'. In that case the server would >> reply with a 504 error because it wouldn't be able to connect with php. >> >> Try this: >> >> <?php >> for ($i=0; $i<100; $i++) { >> phpinfo(); >> sleep (10); >> } >> ?> >> >> as long as sleep() < timeout the server will run fine. >> >> -- >> Octality >> http://www.octality.com/ >> > > Hi Alvaro, > > Thanks for your reply. You are always great at helping us all out! Great > product > too! > > > As for the php loop, I well try that later. I take it this is just to test > the > timeout? A loop reading phpinfo. > > And definitely with the gallery it is GD or ImageMagick doing some > processing. > That one is okay, I just make sure to go through all the new pics myself so > that > they get processed and nobody coming to the site later gets the timeout. > > I wish I could figure out a way for the Zen Cart, PHP, MySQL thing though, > but I > would have to set the timeout to a ridiculously huge number to allow for > that. I > think the client should maybe start pruning their customer list... ;) At > least > the problem is only in the admin interface. > > Is there any number that is kinda the ideal for the site wide timeout? And > how > about the largest number that is feasible? > > Thanks again, > Jason > > _______________________________________________ > Cherokee mailing list > Cherokee [at] lists > http://lists.octality.com/listinfo/cherokee > -- Sent from Gmail for mobile | mobile.google.com _______________________________________________ Cherokee mailing list Cherokee [at] lists http://lists.octality.com/listinfo/cherokee
|