Comments (8)
kdart
commented on May 5, 2024
I'm quite sure the reliability problems are not due to the adb proxy and transport layer.
Two simultaneous UDP iperf sessions didn't show any errors.
⇒ iperf -c localhost -p 7654 -d -i 10 -t 60 -u -b 16M
------------------------------------------------------------
Server listening on UDP port 7654
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to localhost, UDP port 7654
Sending 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 5] local 127.0.0.1 port 40791 connected with 127.0.0.1 port 7654
[ 4] local 127.0.0.1 port 7654 connected with 127.0.0.1 port 40791
[ ID] Interval Transfer Bandwidth
[ 5] 0.0-10.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 4] 0.0-10.0 sec 19.1 MBytes 16.0 Mbits/sec 0.018 ms 0/13605 (0%)
[ 5] 10.0-20.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 4] 10.0-20.0 sec 19.1 MBytes 16.0 Mbits/sec 0.008 ms 0/13606 (0%)
[ 5] 20.0-30.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 4] 20.0-30.0 sec 19.1 MBytes 16.0 Mbits/sec 0.011 ms 0/13605 (0%)
[ 5] 30.0-40.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 4] 30.0-40.0 sec 19.1 MBytes 16.0 Mbits/sec 0.013 ms 0/13605 (0%)
[ 5] 40.0-50.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 4] 40.0-50.0 sec 19.1 MBytes 16.0 Mbits/sec 0.016 ms 0/13606 (0%)
[ 5] 50.0-60.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 5] 0.0-60.0 sec 114 MBytes 16.0 Mbits/sec
[ 5] Sent 81634 datagrams
[ 4] 50.0-60.0 sec 19.1 MBytes 16.0 Mbits/sec 0.013 ms 0/13605 (0%)
[ 4] 0.0-60.0 sec 114 MBytes 16.0 Mbits/sec 0.015 ms 0/81633 (0%)
[ 4] 0.0-60.0 sec 1 datagrams received out-of-order
[ 5] Server Report:
[ 5] 0.0-60.0 sec 114 MBytes 16.0 Mbits/sec 0.014 ms 0/81633 (0%)
[ 5] 0.0-60.0 sec 1 datagrams received out-of-orderOther terminal:
⇒ iperf -c localhost -p 7654 -d -i 10 -t 60 -u -b 16M
------------------------------------------------------------
Server listening on UDP port 7654
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
------------------------------------------------------------
Client connecting to localhost, UDP port 7654
Sending 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 4] local 127.0.0.1 port 41052 connected with 127.0.0.1 port 7654
[ 3] local 127.0.0.1 port 7654 connected with 127.0.0.1 port 41052
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 3] 0.0-10.0 sec 19.1 MBytes 16.0 Mbits/sec 0.011 ms 0/13605 (0%)
[ 4] 10.0-20.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 3] 10.0-20.0 sec 19.1 MBytes 16.0 Mbits/sec 0.012 ms 0/13605 (0%)
[ 4] 20.0-30.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 3] 20.0-30.0 sec 19.1 MBytes 16.0 Mbits/sec 0.020 ms 0/13606 (0%)
[ 4] 30.0-40.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 3] 30.0-40.0 sec 19.1 MBytes 16.0 Mbits/sec 0.003 ms 0/13605 (0%)
[ 4] 40.0-50.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 3] 40.0-50.0 sec 19.1 MBytes 16.0 Mbits/sec 0.011 ms 0/13606 (0%)
[ 4] 50.0-60.0 sec 19.1 MBytes 16.0 Mbits/sec
[ 4] 0.0-60.0 sec 114 MBytes 16.0 Mbits/sec
[ 4] Sent 81634 datagrams
[ 3] 50.0-60.0 sec 19.1 MBytes 16.0 Mbits/sec 0.029 ms 0/13605 (0%)
[ 3] 0.0-60.0 sec 114 MBytes 16.0 Mbits/sec 0.028 ms 0/81633 (0%)
[ 3] 0.0-60.0 sec 1 datagrams received out-of-order
[ 4] Server Report:
[ 4] 0.0-60.0 sec 114 MBytes 16.0 Mbits/sec 0.027 ms 0/81633 (0%)
[ 4] 0.0-60.0 sec 1 datagrams received out-of-orderfrom mobly-snippet-lib.
xpconanfan
commented on May 5, 2024
Two things
- Use tcp
- Does iperf reopen the socket on every send?
from mobly-snippet-lib.
kdart
commented on May 5, 2024
-
I did use TCP, but didn't show it here. The TCP resend will mask dropped packet problems. So UDP is better for that test.
-
No, I'm pretty sure it reuses the same socket for this test.
from mobly-snippet-lib.
xpconanfan
commented on May 5, 2024
Oh, you did a simple two parallel iperf stream... That's not an accurate
simulation of what snippet does...
…On Sep 14, 2017 1:56 PM, "Keith Dart" ***@***.***> wrote:
1.
I did use TCP, but didn't show it here. The TCP resend will mask
dropped packet problems. So UDP is better for that test.
2.
No, I'm pretty sure it reuses the same socket for this test.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#77 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACI25cbo11_DPUwmgkMwRoSZXVRPi9urks5siZLkgaJpZM4PX3rh>
.
from mobly-snippet-lib.
kdart
commented on May 5, 2024
Exactly. ;-) This test mostly verifies basic channel reliability, eliminating that as a possible cause.
from mobly-snippet-lib.
xpconanfan
commented on May 5, 2024
In parallel briefly is not a problem, otherwise your test would never have worked.
The thing is they are flaky.
Also you are using the same port. We use two separate adb forwarding ports...
from mobly-snippet-lib.
kdart
commented on May 5, 2024
OK, for ten simultaneous streams over ten different ports (ten forwards) over 30 minutes shows no performance problems.
device prep:
# for port in $(seq 7650 7659) ; do iperf3 -4 -s -p $port -D ; doneForwards:
⇒ adb forward --list
FA71A0303542 tcp:18998 tcp:8080
FA71A0303542 tcp:20271 tcp:8080
HT73Y0201123 tcp:7654 tcp:7654
HT73Y0201123 tcp:7650 tcp:7650
HT73Y0201123 tcp:7651 tcp:7651
HT73Y0201123 tcp:7652 tcp:7652
HT73Y0201123 tcp:7653 tcp:7653
HT73Y0201123 tcp:7655 tcp:7655
HT73Y0201123 tcp:7656 tcp:7656
HT73Y0201123 tcp:7657 tcp:7657
HT73Y0201123 tcp:7658 tcp:7658
HT73Y0201123 tcp:7659 tcp:7659host side (client):
$ for port in $(seq 7650 7659) ; do (iperf3 -4 -c localhost -p $port --logfile /tmp/iperf3-c-${port}-l -t 1800 )& ; doneSummary:
⇒ grep sender /tmp/iperf3-c-765?-l
/tmp/iperf3-c-7650-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 1 sender
/tmp/iperf3-c-7651-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 1 sender
/tmp/iperf3-c-7652-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 1 sender
/tmp/iperf3-c-7653-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 0 sender
/tmp/iperf3-c-7654-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 1 sender
/tmp/iperf3-c-7655-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 0 sender
/tmp/iperf3-c-7656-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 2 sender
/tmp/iperf3-c-7657-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.7 Mbits/sec 1 sender
/tmp/iperf3-c-7658-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 1 sender
/tmp/iperf3-c-7659-l:[ 6] 0.00-1800.00 sec 7.26 GBytes 34.6 Mbits/sec 0 senderWorst case TCP retransmission was 2 packets.
So, it looks to me that the adb transport performs well and is not a problem. Especially given that the snippet traffic is usually quite small.
Those retransmissions cause a slight delay in message reception and it's the host side client implementation that can't tolerate that delay.
from mobly-snippet-lib.
xpconanfan
commented on May 5, 2024
Cool. Good to know!
Now let's see how we can fix our stuff! :D
from mobly-snippet-lib.
Related Issues (20)
- No release in 3.5 years? HOT 1
- got a crash on android R HOT 2
- Release current master HOT 10
- Minsdkversion upgraded in minor version HOT 3
- Why is minSdk 26, I can compile this with 14? HOT 2
- java.lang.ClassNotFoundException crash
- Add documentation explaining distinction between a snippet that is standalone vs instruments another app.
- Potential racing condition in `SnippetManager.get`
- Make `@RpcMinSdk` work for classes
- Support of RPC scheduling while device is disconnected
- Improve snippet startup procedure to avoid blind waits for connection
- Remove UID as only one session is maintained with current connection logic
- ArrayIndexOutOfBoundsException with Proguard
- Field name is CONSTANT_CASE, but field is not static and final
- Incorrect log tag on itel_a51
- `Log` shows incorrect class name when Proguard is enabled HOT 2
- `presubmit` option broken (race condition?)
- Ex5 for scheduled rpc is broken
- fail to build: error: package android.support.test.rule does not exist HOT 9
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 mobly-snippet-lib.