Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am going to go out and guess that these are static files and you are not passing them through a cgi.</p> <p>From my experience in profiling, and googling profiling, Its all about finding the bottleneck, or optimizing the areas which take the most time, not spending all your effort to speed up the process which takes 5% of your time.</p> <p>I'd like to know more about your setup. What is the response time for one file? What is the return trip time, for a ping? How big are the files?</p> <p>for example if a ping takes 150ms, your problem is your network, not your nginx conf. If files are in the megabytes, its not nginx.</p> <p>If the response time differs between 1 - 30 requests per second, I would assume that something more intense than finer nginx tweaks.</p> <p>Can you shed any more light on the situation?</p> <p>-- update -- I did a benchmark on my out of the box nginx server getting a typical index.php page.</p> <p>When benchmarked from inside the server:</p> <pre><code>roderick@anon-webserver:~$ ab -r -n 1000 -c 100 http://anon.com/index.php This is ApacheBench, Version 2.3 &lt;$Revision: 655654 $&gt; Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking anon.com (be patient) Completed 100 requests Completed 200 requests Completed 300 requests Completed 400 requests Completed 500 requests Completed 600 requests Completed 700 requests Completed 800 requests Completed 900 requests Completed 1000 requests Finished 1000 requests Server Software: nginx/0.8.54 Server Hostname: anon.com Server Port: 80 Document Path: /index.php Document Length: 185 bytes Concurrency Level: 100 Time taken for tests: 0.923 seconds Complete requests: 1000 Failed requests: 0 Write errors: 0 Non-2xx responses: 1000 Total transferred: 380000 bytes HTML transferred: 185000 bytes Requests per second: 1083.19 [#/sec] (mean) Time per request: 92.320 [ms] (mean) Time per request: 0.923 [ms] (mean, across all concurrent requests) Transfer rate: 401.96 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 2 4 1.6 4 9 Processing: 1 43 147.6 4 833 Waiting: 1 41 144.4 3 833 Total: 4 47 148.4 8 842 Percentage of the requests served within a certain time (ms) 50% 8 66% 8 75% 9 80% 9 90% 13 95% 443 98% 653 99% 654 100% 842 (longest request) </code></pre> <p>When benchmarked from my home desktop:</p> <pre><code>roderick@Rod-Dev:~$ ab -r -n 1000 -c 100 http://anon.com/index.php This is ApacheBench, Version 2.3 &lt;$Revision: 655654 $&gt; Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking anon.com (be patient) Completed 100 requests Completed 200 requests Completed 300 requests Completed 400 requests Completed 500 requests Completed 600 requests Completed 700 requests Completed 800 requests Completed 900 requests Completed 1000 requests Finished 1000 requests Server Software: nginx/0.8.54 Server Hostname: anon.com Server Port: 80 Document Path: /index.php Document Length: 185 bytes Concurrency Level: 100 Time taken for tests: 6.391 seconds Complete requests: 1000 Failed requests: 0 Write errors: 0 Non-2xx responses: 1000 Total transferred: 380000 bytes HTML transferred: 185000 bytes Requests per second: 156.48 [#/sec] (mean) Time per request: 639.063 [ms] (mean) Time per request: 6.391 [ms] (mean, across all concurrent requests) Transfer rate: 58.07 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 40 260 606.9 137 3175 Processing: 81 214 221.7 140 3028 Waiting: 81 214 221.6 140 3028 Total: 120 474 688.5 277 6171 Percentage of the requests served within a certain time (ms) 50% 277 66% 308 75% 316 80% 322 90% 753 95% 867 98% 3327 99% 3729 100% 6171 (longest request) </code></pre> <p>My OS is linux, my cpu is 3 years old (it was a $500 server).</p> <p>I have done absolutley nothing to the config file.</p> <p>What does this tell me? nginx is not the problem.</p> <p>Either your server's network blows or AWS is limiting your CPU. I would probably guess both.</p> <p>If the fix is that important, I would get a dedicated server. But thats only as far as my knowledge goes.</p>
    singulars
    1. This table or related slice is empty.
    1. POserver to handle 70 requests a second each with a response time less than 50 milli seconds
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRoderick Obrist
    1. USRoderick Obrist
    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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COnginx forwards the http requests to a cherrypy server running on same machine which responds with some non-static content (~4k bytes) in 3 ms. traceroute from client IP is taking 25-30 ms.
      singulars
      1. PO
      1. UShaltTm
    2. COEverything seems pretty normal. So I would assume that a single http request would be around 50-70 ms. Since no program is really doing anywork I would have to say that cherrypy, or your internet connection is the bottle neck. Try repeating the process with a static file, which should be able to scale up to 10,000 requests per second (or so we have been told)
      singulars
      1. PO
      1. USRoderick Obrist
    3. COInternet connection is not a problem, as server is hosted with AWS. I just did an apache benchmark test with various concurrency parameters. Surprisingly, average/max time to fetch static content of 20 bytes (directly from nginx) is turning out to be a little more than cherrypy serving dynamic content. So, cherrypy too is not a bottleneck.
      singulars
      1. PO
      1. UShaltTm
 

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