Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Instead of managing the <code>KeepAlive</code> settings, which clearly have no real advantage in your particular situation between the 3 options, you should consider switching the Apache to an event or a thread based MPM where you could easily use <code>KeepAlive On</code> and set the <code>Timeout</code> value high.</p> <p>I would go as far as also considering the switch to Apache on Windows. The benefit here is that it's MPM is completely thread based and takes advantage of Windows preference for threads over processes. You can easily do 512 threads with KeepAlive On and Timeout of 3-10 seconds on 1-2GB of RAM.</p> <p><a href="http://www.devside.net/server/webdeveloper" rel="nofollow">WampDeveloper Pro</a> - <a href="http://www.apachefriends.org/en/xampp-windows.html" rel="nofollow">Xampp</a> - <a href="http://www.wampserver.com/en/" rel="nofollow">WampServer</a></p> <p>Otherwise, your only other options are to switch MPM from Prefork to Worker... <a href="http://httpd.apache.org/docs/2.2/mod/worker.html" rel="nofollow">http://httpd.apache.org/docs/2.2/mod/worker.html</a></p> <p>Or to Event (which also got better with Apache 2.4)... <a href="http://httpd.apache.org/docs/2.2/mod/event.html" rel="nofollow">http://httpd.apache.org/docs/2.2/mod/event.html</a></p>
    singulars
    1. This table or related slice is empty.
    1. POApache KeepAlive on API Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USrightstuff
    1. USrightstuff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POApache KeepAlive on API Server
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COas a note, it's not recommended to run XAMPP in a production environment -- not even by the XAMPP developers. Also, the latest releases of XAMPP are known to be extremely buggy; the latest release that's actually stable, I found, was 1.7.3 when I was hunting for something usable a month or so ago.
      singulars
      1. PO
      1. USdamianb
    2. COThanks for feedback! As I mentioned above, a threaded MPM is definitely an option, and given the feedback here seems like I should research it some more. Switching to windows would mean re-writing a lot of other daemons that run on the server. Would the benefits be that great compared to sticking with Linux? I'll mark this as answered because it is the proper solution to my question. I guess the apache tweaking could nearly be a separate one (for short term improvements)
      singulars
      1. PO
      1. USNiall
    3. CONiall, one of the things about Windows that people don't know, is that Apache+PHP+MySQL are bigger here than they are on Linux (more downloads for the win32 binaries are reported from mysql.org since 2009, etc) and the entire set up is rock solid. And the thread-based model is much more efficient here. Not really sure what benefits you'll see (aside from that) except for now being forced to having OS-independent daemons (from a rewrite - might as well make them work on both OSs) OR perhaps being forced to Virtualize your hardware (to run both Windows and Linux)... AKA future benefits.
      singulars
      1. PO
      1. USrightstuff
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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