huge performance drop, any ideas?
This is an open discussion with 10 replies, filed under Troubleshooting.
Search
That is indeed very slow. Try running a local build and see what the performance difference is like - I’m guessing, no nearly as slow.
It runs much faster locally (Output Creation Time 0.1327 s), and also with the old domain name (Output Creation Time around 1 s, but still).
Total Time Spent on Queries (18.9537 s) is very large compared to Output Creation Time (19.6805 s). So, I guess it is database related? Could this be caused by for instance query caching?
Wow, those query times are very large. What processor/server are you on?
1.3159 SELECT * FROM `sm_authors` WHERE `id` = '1' LIMIT 1
That’s a very simple query, so it’s odd that it’s so slow.
I don’t know the server specifications, but they should be ok. I am running another S1.7 install on a similar server (same company).
I asked support about the performance problems and they said that none of the popular (busy) websites on the server using MySQL are experiencing anything similar.
There was a bug in Symphony that caused the session table to get very large. Check your DB and see if that’s the case. You can just clean that table and check to see if that helps with performance.
The session table was not very large, I have applied the fix that was posted in the respective topic.
However, the problem seems to have been fixed automagically. I am getting a whooping Output Creation Time of 0.9393 s.
Far cry from the 34s you had before. Gratz.
Probably related to server load at the time.
I was experiencing similar delays while moving my local install to the server and pointing the first domain name to the server. Is it possible that somehow this can be a DNS issue?
Create an account or sign in to comment.
After a change of the default domainname for a webhosting account, I am experiencing a huge drop in performance of a Symphony 2.0.2 installation.
Here is the debug information for a simple page (there are pages with a lot more datasources and queries, taking even more time). Note how extremely simple queries take a very long time! Also, the debug page is reloaded for all debug elements which results in differing loading time.