Forum > Third party
FreeSpider performance test
motaz:
Now after these performance results I could write any huge web application with more confidence.
Before this test I was thinking to add ISAPI/ or .so (Apache extension) for shared code, to reduce memory consumption and faster response. But it seems that we will stuck on the performance of the database, specially when it is outside web server. So that there may be a little difference between ISAPI and CGI
jarto:
Keep in mind that performance usually suffers quite a bit when the web server and the database gets hit with many simultaneous requests. I suppose these httperf-requests were sequential?
motaz:
Yes, may be the Apache server, or httper tester do not send all requests at the same time, may be the Apache is doing some queuing mechanism.
May be because of update command. When I change it to query database only, it was more faster.
Luckily update actions are very few compared with query for normal database systems.
jarto:
I guess I didn't explain myself well enough. My comment was mainly on your estimations of how many active users you can handle. I'm pretty sure httperf does all those 2500 requests sequentially. Apache doesn't have to queue anything and at no point are there multiple threads fighting (and waiting) for the same resource. No locks are slowing you down.
Things change quite a bit when many threads are running at the same time. That will happen if you have 2500 users. At that point you may notice, that one run doesn't take 0.05 seconds any more. It starts to take 0,5 seconds, 2 seconds, even more. And as the running time gets longer, the number of simultaneous threads increases, making the situation quickly worse. Rush hour slows things down on the information highway as well as the real highway :)
Can you try this: Run two simultaneous long httperf runs from two terminals. When these two are running, run a third, shorter httperf run and check, how fast that third one is.
motaz:
I have selected 2500 connections in httper to get these results:
httperf --client=0/1 --server=localhost --port=80 --uri=http://localhost/cgi-bin/news/detail?id=-22 --send-buffer=4096 --recv-buffer=16384 --num-conns=2500 --num-calls=1
request rate was 39 request per second:
Request rate: 39.7 req/s (25.2 ms/req)
So that average concurrent connections was 39, I suppose.
Navigation
[0] Message Index
[#] Next page
[*] Previous page