Last modified: 2014-06-17 09:24:56 UTC
Created attachment 15568 [details] load time load.php The new version 1.23 makes every page load for about 10 seconds or more because of the call for the file load.php: /load.php?debug=false&lang=de&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=20140605T110156Z Attached screenshot. PHP 5.5.12 NGINX
Thanks for taking the time to report this! The screenshot says debug=true while your comment says debug=false? Which PHP version is this about?
I've tested the signle request with debug=true cause i was hoping i'm getting new information - i didnt :| As described its PHP 5.5.12 running on NGINX. Here is the complete page-load for a single request of the /index.php: http://www.landeszeitung.de/mediawiki.png
The most time i see in the picture is the "waiting phase", am i right? In the waiting phase the browser wait's for the first response of the server, so maybe the problem is with the server? :)
Update: Even when executing the index.php by hand (via cmd) it takes ages to get a response. The wait starts when with the following line: require __DIR__ . '/includes/WebStart.php'; I'll keep investigating this.
I've tracked the problem to: ob_start( 'wfOutputHandler' ); in: includes/WebStart.php
The problem resides inside this output buffer - i'll keep tracking this once i'm back home.
(In reply to fs from comment #6) fs: Any luck?
Yes so here is what i've found out: IF i'm using an external database (in my testcase MySQL) the Wiki took approx 9 sec per site (means per PHP-Script so index.php + load.php = 18 sec). IF i'm using a MySQL-Server on the machine itself - it works flawlessly. Im quite sure its not our network because we're running multiple MySQL-Clusters here with the same setup. Any Ideas?
MySQL-Version 5.6
In my projects i often used this, when external mysql connections are slow: http://bobbyallen.wordpress.com/2007/11/02/slow-connections-on-remote-mysql-servers/ Can you check, if you have skip-name-resolve enabled? Kind regards Florian
Hello Florian, this did resolve the issue. However im not sure why the DNS caused the problems. I will track this problem and try to identify the exact error in my case - so long i mark this as solved. Thanks again.
> im not sure why the DNS caused the problems Without skip-name-resolve, mysql will try to resolve the hostname of the clients, mainly to match hostnamens and IP adresses in grant table. If your client isn't in same network like the mysql server and has no reverse hostname in dns service, the mysql is asking, then the hostname resolve fails, but takes time :) If you disable (or skip) the name resolve, mysql don't resolve hostnamens in any case. The problem using this is, that hostnamens in grant table are useless, you must need ip adresses :) See http://dev.mysql.com/doc/refman/4.1/en/dns.html for further information.
