Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It can be any number of things, including that your computer just can't handle the load. I can give you a few pointers where to look though.</p> <p>You are getting some errors returned <code>Failed requests: 68</code>. Look into the apache logfiles, they might indicate the problem. If you don't find anything in them make sure logging is enabled and your config file has the correct log level set. Your <code>VirtualHost</code> definition should contain something like</p> <pre><code> LogLevel debug CustomLog /var/log/apache2/access-localhost.log vhost_combined ErrorLog /var/log/apache2/error-localhost.log </code></pre> <p>Use <code>LogLevel debug</code> only for debugging. You'll want to set it to <code>warn</code> or <code>error</code> for production.</p> <p>Enable error logging in php.ini and your scripts and check your php error log for any problems.</p> <p>Make sure your apache2.conf is configured correctly, especially the mpm module. Here is a standard, albeit far from perfect configuration:</p> <pre><code>&lt;IfModule mpm_prefork_module&gt; StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 &lt;/IfModule&gt; &lt;IfModule mpm_worker_module&gt; StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 &lt;/IfModule&gt; </code></pre> <p>Make sure you have enough RAM for that, you'll need around 1GB for apache2 only (at least under linux)</p> <p>You can also try to check performance against a small static text file (around 2kb) and see what that performance looks like. After that check against the simple <code>&lt;? php echo 'Hello World!' ?&gt;</code> to see the performance impact of the php interpreter. Both tests should give you an indication of what your apache is capable of with the current configuration. If the performance is acceptable in both tests, it's your app that's slow. </p> <p>Another thing to try is disabling concurrency in your test and see if that helps. That would indicate concurrency problems in your app or database access.</p> <pre><code>ab -c1 -t60 http://sf2.cities.localhost/app.php </code></pre> <p>If it's still slow, google <code>apache performance tuning</code> and (assuming you use MySQL as your database) <code>mysql performance tuning</code></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload