apachetop | apachetop watches a logfile
kandi X-RAY | apachetop Summary
kandi X-RAY | apachetop Summary
apachetop watches a logfile generated by apache (in standard common or combined logformat, and generates human-parsable output in realtime. see the install file for ./configure options (there's a few newly added since v0.11). several commandline options dictate some of its' behaviour: -f logfile select which file to watch. specify this option multiple times to watch multiple files. -h hits | -t time these options are mutually exclusive. specify only one, if any at all. they work as follows. apachetop maintains a table of information internally containing all the relevant information about the hits it's seen. this table can only be a finite size, so you need to decide how big it's going to be. you have two options. you can either: use -h to say "remember hits" or use -t to say "remember all hits in seconds". -q instructs
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of apachetop
apachetop Key Features
apachetop Examples and Code Snippets
Community Discussions
Trending Discussions on apachetop
QUESTION
Probably explanation is simple - but I couldn't find answer to my question:
I am running jmeter test from one VM (worker) to another (target). On worker I have jmeter with 100 threads (100 users). On target I have API that runs on Apache. When I run "apachetop -f access_log" on target, I see only about 7 req/s. Can someone explain me, why I don't see 100 req/s on target?
In test result in jmeter I see always 200 OK, so all request are hitting the target, and moreover target always responds. So I am not dropping any requests here. Network bandwidth between machines is 1G. What I am missing here?
Thanks, Daddy
...ANSWER
Answered 2017-Feb-08 at 19:29Your target load = 100 threads ( you are assuming it should generate 100 req/sec as per your plan)
Your actual load = 7 req / sec = 7*3600 / hour = 25200
Per thread throughput = 25200 / 100 threads = 252 iterations / thread / hour
Per transaction time = 3600 / 252 = 14.2 secs
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install apachetop
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page