It's also worth noting that you sometimes lose stability using eAccelerator. I've experienced a notable number of apache segfaults trying to squeeze out some performance, where as .pyc comes out of the box with no instability.
-Wes On May 12, 10:30 am, rcs_comp <[EMAIL PROTECTED]> wrote: > Mat, > > You are right, I should have done that. I setup eAccelerator for IIS > in both FastCGI and ISAPI modes. Unfortunately, I could not get > eAccelerator working in non-thread-safe mode with FastCGI (which is > what Microsoft recommends). Here are my results: > > PHP ISAPI eAccelerator Symfony: 25.06 > PHP FastCGI eAccelerator Symfony (thread-safe mode): 23.41 > PHP ISAPI Symphony (no accelerator): 11.36 > > Even if I got FastCGI and eAccelerator working in non-thread-safe > mode, I don't think it would come close to touching PyISAPIe and > Django in these tests. > > Thoughts? > > On May 12, 6:19 am, "Mat" <[EMAIL PROTECTED]> wrote: > > > Dunno if you can do it on IIS (cant say ive ever tried), but try installing > > a PHP accelerator such as eaccelarator or APC, both are open source. This > > will cache your php files similar to *.pyc in python, and should give you a > > x8-x10 boost. It is not really a fair test without it :) It is how we run > > all out symfony servers and they wouldn't cope otherwise! > > > Mat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
