Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The very first thing you should be checking is whether the clients are actually using the keepalive functioality at all. I'm not sure what you mean by an 'API server' but if its some sort of webservice then (IME) its rather difficult to implement well behaved clients using keepalives.(See %k directive for mod_log_config).</p> <p>ALso, we really need to know what your objectives and constraints are? Performance / capacity / low cost?</p> <p>Is this running over HTTP or HTTPS - there's a big difference in latency.</p> <p>I'd have said that a keeplive time of 10 seconds is ridiculously high - not low at all.</p> <p>Even if you've got 90 clients holding connections open, 4Gb seems a rather large amount of memory for them to be using - I'e run systems with 150-200 concurrent connections to complex PHP scripts using approx 0.5Gb over resting usage. Your figures of 250 + 90 x 20M only gives you a footprint of about 2Gb (I know is not that simple - but its not much more complicated). </p> <p>For the figures you've given I wouldn't expect any benefit - but a significantly bigger memory footprint - using anything over 5 seconds for the keepalive. You could probably use a keepalive time of 2 seconds without any significant loss of throughput, But there's no substitute for measuring the effectiveness of various configs - and analysing the data to find the optimal config. </p> <p>Certainly if you find that your clients are able to take advantage of keepalives and get a measurable benefit from doing so then you need to find the best way of accomodating that. Using a threaded server might help a little with memory usage, but you'll probably find a lot more benefit in running a reverse proxy in front of the webserver - particularly which SSL.</p> <p>Besides that you may get significant benefits through normal tuning - code profiling, output compression etc.</p>
    singulars
    1. This table or related slice is empty.
    1. POApache KeepAlive on API Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsymcbean
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt's just a web service running on a server. You are spot on with the memory footprint, it is roughly 2GB in total (1.5GB RAM in use on server in other areas). I suggested 10 seconds for the following reason: If the client connects every 3 seconds and the apache process stays alive for 10 seconds, would the same process not remain with the client until they stop making requests (ie: Pretty much working like a persistent connection)? Short term, tweaking Apache is our only option really. Long term, threaded MPM, nginx, json-rpc are all things I'll look at
      singulars
      1. PO
      1. USNiall
 

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