search

Robert-Emerson / cs4414-ps3

MIT License
0 stars 0 forks source link

Exploration 1: Benchmark #9

Open nathantypanski opened 10 years ago

nathantypanski commented 10 years ago

Try benchmarking your zhptto server from PS1 and the current zhtta server. Which has better performance? Can you explain the differences you see in the benchmark results?

(You don't need to turn in anything for this, but should be prepared to talk about how you benchmarked your server and what you learned from it at your demo.)

I'm placing the explorations in here as well as the problems themselves, and tagging this one as a question. That way we can keep (most) of our work related to the problem set in one place.

nathantypanski commented 10 years ago

Related: 5938250243

add script to automate benchmarking

nathantypanski commented 10 years ago

Related: cdd88f6

File for exploration1

nathantypanski commented 10 years ago

I don't have an EC2 server (and I'm too lazy to make one), but I ran our code on my personal server from DigitalOcean and got us on the leaderboards. Since nobody else has run their server on the boards yet, it still managed to place.

http://128.143.136.170:4414/leaderboard.html

It came in 3rd place, behind both the reference solution and Apache2, but that could just be because my server is slow. I would imagine EC2 has better overall performance than my VPS.

Edit: Oh, I just realized the reference solution is supposed to be the one with all the problems completed! In that case, the placement is not very bad considering we don't even have caching yet.

Httperf output from the test run:

 Queuing for benchmark, please wait...
Benchmark starts, please wait...
httperf --server  --port 4414 --rate 10 --num-conns 60 --wlog=y,/home/grader/minigrade/tests/zhtta-test-NUL.txt
httperf: warning: open file limit > FD_SETSIZE; limiting max. # of open files to FD_SETSIZE
httperf --client=0/1 --server= --port=4414 --uri=/ --rate=10 --send-buffer=4096 --recv-buffer=16384 --num-conns=60 --num-calls=1
Maximum connect burst length: 1

Total: connections 60 requests 60 replies 60 test-duration 80.073 s

Connection rate: 0.7 conn/s (1334.6 ms/conn, <=11 concurrent connections)
Connection time [ms]: min 24.3 avg 4298.8 max 74172.7 median 25.5 stddev 14260.5
Connection time [ms]: connect 12.1
Connection length [replies/conn]: 1.000

Request rate: 0.7 req/s (1334.6 ms/req)
Request size [B]: 74.0

Reply rate [replies/s]: min 0.0 avg 0.7 max 8.0 stddev 2.0 (16 samples)
Reply time [ms]: response 12.7 transfer 4274.0
Reply size [B]: header 54.0 content 4896774.0 footer 0.0 (total 4896828.0)
Reply status: 1xx=0 2xx=51 3xx=0 4xx=9 5xx=0

CPU time [s]: user 13.26 system 66.57 (user 16.6% system 83.1% total 99.7%)
Net I/O: 3583.3 KB/s (29.4*10^6 bps)

Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0
Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0