By ludberg on
As the title says, I'm having trouble accessing admin/content.
The Call Stack can be found here: http://i.imgur.com/BlP3u.png
I'm running a pretty plain install and I'm using the basic Bartik theme. The problem has started to occur after I added some 100 nodes.
Edit: I know about max execution time in php.ini but that is not a permanent solution. If a page takes more than 30 seconds to load, something is clearly wrong.
Edit 2: This occurs whether or not I have Overlay activated or not
Comments
Caching
Have you employed any caching?
http://drupal.org/node/326504
Is Devel running?
( I like the Boost module)
Are you running Facebook connect? I ask because lately Facebook has randomly slow responding and I'm wondering if that's what's hanging everything up?
Yes, I have everything ticked
Yes, I have everything ticked under Performance.
Also, I have installed APC.
I just installed Devel and got the following result for the front page.:
Executed 142 queries in 77.41 ms. Queries exceeding 5 ms are highlighted. Page execution time was 5862.39 ms. Memory used at: devel_boot()=4.68 MB, devel_shutdown()=50.11 MB, PHP peak=51.25 MB.
I have turned off Update manager and database logging.
Other modules I have enabled are:
Block
Contact
Contextual links
Fields UI
Help
Locale
PHP Filer
RDF
Search
Administration menu
Wysiwyg
Chaos tools
Facebook API
IMCE
Meta tags
Advanced help
Facebook Like Button
Global Redirect
Node clone
Path auto
phpBBforum
token
Transliteration
Google analytics
Views
XML Sitemap
I'm using my-large.ini for MySQL and have increased the following:
innodb_buffer_pool_size = 1000M
innodb_additional_mem_pool_size = 500M
In php.ini I have changed these:
max_input_time = 180
max_input_nesting_level = 64
realpath_cache_size = 2M
WAMP
- apache 2.2.21
- php 5.3.8
- mysql 5.5.16
Computer:
Intel(R) Core i7-2600K 3.40GHz
Memory: 8gb
SSD
Print screen from Chrome, network debug
http://i.imgur.com/VHWcJ.png
Let's try
Things to try:
1.) disabling the timeout culprit and find out if there is an issue going on there. Since BaseFacebook seems to run okay up to line 842, (what's on line 842 btw?) my first test would be disabling facebook modules and apps. It could very well be something else, but since that's where your log says the timeout occured let's start there.
(Also, I've been poking around the net for timeout errors associated with base_facebook.php and there seems to be a bit going on there. You might want to look for deeper errors to get at what's really going on. (for example, several folks had "uncaught" curl errors that were causing timeouts..)
2.) What memory size have you set in APC? (perhaps it is starting to fragment?)
3.) Did you make any config changes prior to this?
4.) Continue to use Devel to track queries - this may well sniff out the issue...
5.) increase your realpath_cache_size
6.) try other browsers to see if the timeout still occurs...
7.) InnoDB, MyISAM? Some drupalers report that MyISAM under WAMPP significantly improved speed ...
I narrowed it down to
I narrowed it down to Facebook Connect. On pages where this is not visible, I have a total execution time of 400 ms and 8000ms otherwise.
Thanks for your help locating the problem!
Edit: update for future readers
There is a discussion going on about this problem here: http://drupal.org/node/1249026
One way to get around this for now is to have selected as the default app.
Great!
Great! Well, not so great in that a solution still needs to be found for FaceBook ... but Great for you that you at least know what's going on!
Be sure you post back here when the ultimate solution is found so that others can breathe easier too!