![]() ![]() ![]() Did the realpath thingy to the php.ini and in Google Chrome, I have to say that the performance is borderline "snappy" :) Works just dandy for all of my Joomla development, but with Drupal 6 core or the Acquia Drupal package, this combo was painfully slow. I am using the latest version of The Uniform Server (4.1 'Mona') running on my old "boat anchor" COMPAQ Evo N600c laptop, Win XP and a paltry 512 MB RAM. I was experiencing the same issues as those in this thread Modules were especially slow. So, testing the ideas of tagawa will be next.įirst post in the Drupal forum from a "dyed-in-the-wool" Joomla! type :) 300 + Joomla installs to date so not a complete "noob" to the CMS scene :) Sure do like a LOT of what Drupal has to offer (now that I am more experienced with this type of environment) but there are some things here that I am still trying to "wrap my head around". Sometimes it helps to just activate or deactivate only a few models at a time and not the whole parade of goodies at once. ![]() Opening or saving the modules page is always slow as it checks all modules. So one might have to fidle a bit to see where the variables are that need adjusting. Please note: The php.ini file might be in different locations depending on which wamp is used (A2T is under Windows / WS2f is under :\wamp\bin\apache\Apache2.2.11\bin\ and under :\wamp\bin\php\php5.2.8\ or whichever php version and there are more ".ini" files in use such as phpforapache.ini under :\wamp\bin\php\php5.2.8\. For WampServer I had to increase the "max_execution_time" to 90 secs in the php.ini. It is a little slower than Apache2Trial - which was doing well on standard drupal settings. Using WampServer is convinient for the interface and ease of use. Well, I have WampServer 2.0f running now for a week and one thing I found is that all Wamps need a bit of time to "warm". Some improvements would be greatly welcomed. I have to say, that once I install the sites on a host server (I have 2 years of great service from 5quithosting in the UK sofar) Drupal runs faster, but not fast enough to the point that some clients wonder about the slack response times. time that comes in at 30 secs - "max_execution_time = 30". sites.īy the way with a2t I never had to change the php.ini default exec. I use also a no-frills Safari browser for testing and while it might be a little bit faster as a browser, it suffers the same slow response times as Firefox on the local installations for various Drupal 6.8. I use Online Armour as Firewall and lots of add-ons in Firefox - to me it seems there is no difference if I disable Online armour or the add-ons in Firefox. With Xampp loading modules and saving changes timed me out all the way. I tried all sorts of suggestions, but had to go back to a2t. Great interface, setup and encouraging for newcomers. The new release of Xampp (1.7.xx) looks great and it now supports clean URLs - so I tied it and replaced my apache2triad installation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |