By omigosh on

My site seems to work fine when I'm not developing it, but when I'm logged in it's so slow I can't hardly bear working on it. I'm working on a production site, not through MAMP, but that was just as slow. In fact I found the production-site method slightly faster.

Is this normal? Is there a special site that works best with Drupal? How slow do other developers find Drupal? I've done a fair bit of editing on my own in PHP and MySQL, and my sites have always worked normally throughout, using the same server.

Is there anything I can do to speed things up during development work? I'm spending half my time just watching the pages refresh.

Comments

Anonymous’s picture

Anonymous (not verified) commented

You're asking a pretty general question as long as you don't provide any specs about your site and its hosting environment.

Could be you have turned on Drupal's caching, so from an anonymous visitor's point of view your site may have good speed. When you log in to create content or to develop Drupal's standard caching isn't in effect and therefore page generation always takes more time. How much more depends on so many factors it wouldn't make sense to list all possibilities without having more detailed information from your side.
But the described effect is especially the case on some shared hosting environments with centralized and always rather busy database servers.

omigosh’s picture

omigosh commented

I found my site speeded up a bit after I restarted my browser, but it's still very slow. I've trolled through a few other Drupal sites, just as an unrecognized user, and they seem slower than most other sites. If anybody's reading this, I'd just like to know if that is also their experience.

Thanks

Anonymous’s picture

Anonymous (not verified) commented

Have you installed and activated the Devel module and configured it to gather database query information and show those along with the page timer? Devel will output these debug information at each page's end. It shows you how long it took togenerate the current page (that's the PHP execution time) and how much time has been spent executing how many sql queries. This gives a first indication about where the bottleneck may be and which direction to investigate further.