i just upgraded my live site to 2.1.2 from 1.12.x and am not seeing the kind of fast response times i had seen in my test site that runs the same code on the same hardware.
when i enabled the developer tools feedback panel in the live site, i saw that the live site is generating dramatically more SQL queries per page than the test site is. my only thoughts on why that could be is that there is that the live site runs on a different language collation (latin) to the test site (utf8) and maybe the live site's database has errors i don't know about causing more queries to be run somehow?!
at this point i have no real clue as to what is really causing this - so any input here would be appreciated.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
what's the best way to get a breakdown of the queries in that query count?
Elgg 2.1 has this: https://github.com/Elgg/Elgg/blob/2.1/elgg-config/settings.example.php#L229-L244
oh ok, i missed that. i uncommented the lines in settings.php and added a secret key but i see nothing in the log. do i need to add a reference to the secret key somewhere else?
i just looked through the code for the profiler function but didn't see any reference to the secret key other than in the settings.php file. who has successfully run the profiler here? did you do anything other than comment out the lines in settings.php to get it to run?
Profiling data is in the browser console.
i know that is the intended result, but there is nothing in the browser console here - in firefox.
You need to add the key to the URL or remove the check feom settings.php to enable it for all pages.
Also check your boot cache setting (should be documented in the default settings.php).
You can also log all queries by setting the debug level to Notice.
aha, ok. i did test it with no key entered and that didn't work, so i thought something else was needed. thanks.
now i see the tree object in the console - looks like it's easiest to examine it in chrome's log, rather than firefox.
i had been testing without the boot cache as i knew nothing about it and the relevant lines didn't make it across to my settings.php file. i did find it earlier and enabled it for both my test and live sites - however, that is not part of why there is a huge amount of extra queries present on my live site compared to my test site.
- Previous
- 1
- 2
- Next
You must log in to post replies.