Comments (12)
Meny, could you describe scenario of failure if it is differ from described
below.
Investigation note:
vperf r1868:
1. done more than 1000 tests as
vperf sr --tcp
vperf ul -i 10.10.10.51 --tcp --pps=X
where X is value in interval (1..200)
Result:
no issue observed
2. ran client w/o server as
vperf ul -i 10.10.10.51 --tcp --pps=1
Result:
displayed output from issue description
3. ran client as UDP
vperf sr
vperf ul -i 10.10.10.51 --tcp --pps=1
Result:
displayed output from issue description
Conclusion:
Output you observed is valid case for scenarios 2 and 3.
Issue is not noticed in 1 case.
#3
Original comment by [email protected]
on 4 Apr 2011 at 6:26
from sockperf.
Meny`s note:
Scenario 2 doesn't make any sense, there is no tcp connection.
I saw it when I ran scenario 1 with small pps (approx 1-200), and also on UDP
(scenrio 3 without (!!) the --tcp flag)
Original comment by [email protected]
on 4 Apr 2011 at 6:27
from sockperf.
Igor`s note:
Meny,
- could you send me output from server and clients sides got with d option in
command line for the 1th scenario (I can not reproduce one);
as for UDP that it confuses me because error "Can`t connect socket" can not be
displayed during UDP connection (it is TCP specific);
Original comment by [email protected]
on 4 Apr 2011 at 6:27
from sockperf.
Meny`s note:
D_PRELOAD=libvma.so vperf under-load -i 1.1.1.1 --pps 1
vperf: version #2.4.1871
vperf: No VMA version info
vperf[CLIENT] send on:vperf: using recvfrom() to block on socket(s)
[ 0] IP = 1.1.1.1 PORT = 11111 # UDP
vperf: Warmup stage (sending a few dummy packets)...
vperf: Starting test...
vperf: Test end (interrupted by timer)
vperf: Test ended
vperf: ========= Printing statistics for Server No: 0
vperf: No messages were received from the server. Is the server down?
vperf: Test end (interrupted by signal 2)
[root@ronaldo2 ~]# D_PRELOAD=libvma.so vperf under-load -i 1.1.1.1 --pps 10
vperf: version #2.4.1871
vperf: No VMA version info
vperf[CLIENT] send on:vperf: using recvfrom() to block on socket(s)
[ 0] IP = 1.1.1.1 PORT = 11111 # UDP
vperf: Warmup stage (sending a few dummy packets)...
vperf: Starting test...
vperf: Test end (interrupted by timer)
vperf: Test ended
vperf: ========= Printing statistics for Server No: 0
vperf: No messages were received from the server. Is the server down?
vperf: Test end (interrupted by signal 2)
[root@ronaldo2 ~]# D_PRELOAD=libvma.so vperf under-load -i 1.1.1.1 --pps 100
vperf: version #2.4.1871
vperf: No VMA version info
vperf[CLIENT] send on:vperf: using recvfrom() to block on socket(s)
[ 0] IP = 1.1.1.1 PORT = 11111 # UDP
vperf: Warmup stage (sending a few dummy packets)...
vperf: Starting test...
vperf: Test end (interrupted by timer)
vperf: Test ended
vperf: ========= Printing statistics for Server No: 0
vperf: Test end (interrupted by signal 2)
vperf: [including warmup] RunTime=1.100 sec; SentMessages=110;
ReceivedMessages=1
vperf: No valid observations found. Try increasing test duration and/or
--pps/--reply-every parameters
[root@ronaldo2 ~]# D_PRELOAD=libvma.so vperf under-load -i 1.1.1.1 --pps 200
vperf: version #2.4.1871
vperf: No VMA version info
vperf[CLIENT] send on:vperf: using recvfrom() to block on socket(s)
[ 0] IP = 1.1.1.1 PORT = 11111 # UDP
vperf: Warmup stage (sending a few dummy packets)...
vperf: Starting test...
vperf: Test end (interrupted by timer)
vperf: Test ended
vperf: ========= Printing statistics for Server No: 0
vperf: [including warmup] RunTime=1.100 sec; SentMessages=220;
ReceivedMessages=2
vperf: No valid observations found. Try increasing test duration and/or
--pps/--reply-every parameters
vperf: Test end (interrupted by signal 2)
[root@ronaldo2 ~]# D_PRELOAD=libvma.so vperf under-load -i 1.1.1.1 --pps 300
vperf: version #2.4.1871
vperf: No VMA version info
vperf[CLIENT] send on:vperf: using recvfrom() to block on socket(s)
[ 0] IP = 1.1.1.1 PORT = 11111 # UDP
vperf: Warmup stage (sending a few dummy packets)...
vperf: Starting test...
vperf: Test end (interrupted by timer)
vperf: Test ended
vperf: ========= Printing statistics for Server No: 0
vperf: Test end (interrupted by signal 2)
vperf: [including warmup] RunTime=1.100 sec; SentMessages=330;
ReceivedMessages=3
vperf: ====> avg-lat=140.567 (std-dev=0.000)
vperf: # dropped packets = 0; # duplicated packets = 0; # out-of-order packets
= 0
vperf: Summary: Latency is 140.567 usec
vperf: Total 1 observations; each percentile contains 0.01 observations
vperf: ---> <MAX> observation = 140.567
vperf: ---> percentile 99.99 = 140.567
vperf: ---> percentile 99.90 = 140.567
vperf: ---> percentile 99.50 = 140.567
vperf: ---> percentile 99.00 = 140.567
vperf: ---> percentile 95.00 = 140.567
vperf: ---> percentile 90.00 = 140.567
vperf: ---> percentile 75.00 = 140.567
vperf: ---> percentile 50.00 = 140.567
vperf: ---> <MIN> observation = 140.567
Original comment by [email protected]
on 4 Apr 2011 at 6:28
from sockperf.
Igor`s note:
Meny,
It is not clear how the latest output relates described issue. Output looks
reasonable because in ul test server answers in 100 packets by default.
It does not include requested output for scenario 1 also.
Original comment by [email protected]
on 4 Apr 2011 at 6:28
from sockperf.
imported from: http://argus-bg.dnsalias.org/issues/759
Original comment by [email protected]
on 4 Apr 2011 at 7:11
from sockperf.
The output shows that there is no traffic when using smal pps (1-200)
When I ran it with pps = 300, traffic passed.
Original comment by [email protected]
on 6 Apr 2011 at 8:17
from sockperf.
this means you reproduced the bug. please fix it.
Original comment by [email protected]
on 6 Apr 2011 at 9:01
from sockperf.
Traffic info can be recieved from
"vperf: [including warmup] RunTime=X sec; SentMessages=Y; ReceivedMessages=Z"
line on client side
and
"sockperf: Total messages X received and handled" line on server side;
Meny probably means "Observation" info. In this case it can be explained by
following as sockperf truncates little interval of time from the start of test
and some interval at the end so as result some measurement are cut off from
observation.
Avner, could you make clear what is a reason of doing it and if it is still
needed.
Original comment by [email protected]
on 8 Apr 2011 at 11:57
from sockperf.
Igor, we are ignoring first 50millisec and last 50 millisec. That's all I
remember. The reason is cleaner results under load.
It should not affect you in test of few seconds.
Original comment by [email protected]
on 10 Apr 2011 at 6:30
from sockperf.
"Observation" info is not seen because the first and last measurements were
omitted.
I have not seen the reason to do it and corrected in r47 (it looks as a bug).
There is open question related 50millisec time after test start and before test
end.
Having it can cut off the first measurement from final result set for example
on --reply-every=1.
Avner, I have not found any reason to keep this.
Original comment by [email protected]
on 11 Apr 2011 at 3:01
from sockperf.
r47 was reverted since skipping few first and few last reply-packets is part of
tool concept.
User should follow print recommendation to increase test duration and/or
increase pps/replies in case observations are not enough.
Original comment by [email protected]
on 13 Apr 2011 at 5:32
- Changed state: Invalid
from sockperf.
Related Issues (20)
- sockperf pp tcp mode: can't set --mps under 5000 messages per second HOT 2
- sockperf playback tcp mode on RaspberryPi: Error, illegal time or size at line #4 HOT 1
- t assign
- ERROR: _seqN > m_maxSequenceNo in v3.7 HOT 9
- ping-pong on Arm seems does not respect --mps parameter HOT 3
- Configure attempts to compile c++ code with gcc but not with g++ HOT 2
- print date&time every time it is executed HOT 4
- Floating point exception with --histogram HOT 2
- How to read sockperf output HOT 4
- _seqN > m_maxSequenceNo (100% reproducible on ppc64le architecture) HOT 4
- sockperf tcp mode: 100% cpu HOT 7
- Void function returing according to the documentation a value
- Non documented argument of function process_buffer
- Confusing commenting out code
- Need help on Sockperf configuration on Azure Ubuntu instances HOT 9
- sockperf server hung on sockperf: [tid1269] using recvfrom() to block on socket(s) HOT 4
- how to install sockperf onwindows 10 and window 11 machines HOT 8
- RedHat support HOT 2
- Simetimes I get "No messages received" and have to retry HOT 3
- sockperf crashed due to segment fault when using libvma HOT 13
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sockperf.