Significant speed drop in file push/pull operations on version 1.0.26065.0 compared to 0.9.25070

[worldcitymobile96-oss]

Problem

File push and pull speeds are extremely slow in the latest version (1.0.26065.0).

Details

• Version 0.9.25070_x64: Speed is very fast and works perfectly.
• Version 1.0.26065.0: Speed dropped significantly on the same PC, phone, and cable.

Please check why the latest update has slowed down the data transfer.

[Alex4SSB]

Well this is the first time I'm hearing this - it might be that your phone / PC setup is having trouble with AdvancedSharpAdbClient implemented in v0.9.25100. It is essentially skipping the PC side ADB server for push/pull and opens direct streams with the phone. This not only allowed us to get way more accurate and reliable progress updates, but also allows opening parallel streams which allows us to achieve greater speeds than classic ADB when transferring several large files (doesn't affect the speed of single file transfers).

So I have several questions for you:

1. Android version (phone model?)
2. Windows version
3. ADB / platform tools version
4. USB 2 or 3? Have you tried WiFi / mDNS?
5. Transfer scope: single file (size?) / multiple files (average size? how many?) / folder (how many files inside? sub-folders?)

[worldcitymobile96-oss]

Well this is the first time I'm hearing this - it might be that your phone / PC setup is having trouble with AdvancedSharpAdbClient implemented in v0.9.25100. It is essentially skipping the PC side ADB server for push/pull and opens direct streams with the phone. This not only allowed us to get way more accurate and reliable progress updates, but also allows opening parallel streams which allows us to achieve greater speeds than classic ADB when transferring several large files (doesn't affect the speed of single file transfers).

So I have several questions for you:

1. Android version (phone model?)
2. Windows version
3. ADB / platform tools version
4. USB 2 or 3? Have you tried WiFi / mDNS?
5. Transfer scope: single file (size?) / multiple files (average size? how many?) / folder (how many files inside? sub-folders?)

Here are the answers to your questions based on my usage:

1. Android version & Phone model: I run a mobile shop, so I test this on many different devices daily. I face this exact speed issue on all devices—both newer Android versions/models and older ones.
2. Windows version: Windows 11 Pro
3. ADB / platform tools version: In version 0.9, I was using the latest official ADB platform-tools folder. In version 1.0, I am using the default built-in folder.
4. USB 2 or 3 / WiFi: I always use high-quality USB cables. I do not use WiFi or mDNS for transfers.
5. Transfer scope: I transfer both single large files and heavy folders like WhatsApp data (which ranges from 10GB, 20GB, 30GB, up to 50GB with thousands of small files).

The old 0.9 version finishes these massive WhatsApp data transfers very quickly, but the new 1.0 version takes a very long time to complete the exact same data.

[Alex4SSB]

Just to clarify the ADB - the version is displayed in the Settings page -> first group title (ADB XX.X.X). Can you check that please?

Also, how much slower is the new version? What transfer speeds do you get in the new version, and what were the speeds in the old one?

The latest version achieves 35MB/s on a 2018 laptop with i5 CPU running Windows 10, connected via the original charging USB 2.0 cable to OnePlus 3T running Android 9 (WiFi sometimes surpasses this). So I don't see a problem with the app and the transfer method, and moreover I don't see much I can investigate here. Do you have another PC you can test this with? Please use the latest ADB - 37.0

[Alex4SSB]

@worldcitymobile96-oss Do you have an update?

[ilgrank]

Hi
While I can't speak for the original poster , I can too say there's something not working (for me) in the new branch.
My findings so far, comparing 0.9.26040 vs 1.0.26072, both using ADB v37:

• Speed is lower (1.6Mb/s against 9.8Mb/s)
• ADB frequently hangs
• often, 0-bytes files get created:

My scenario:

• i9 10940x with Samsung 990 Pro nvme drive, Windows 10 pro 22h2
• connected using USB3 10GBps port and certified cable on a Samsung S23 Ultra
• transferring 38200 files from the DCIM/Camera folder, using Merge/replace to destination
• Tried with both polling enabled/disabled during pulls
• 0.9.25070 has interface non-responsive during transfers,but still goes on and the icon on taskbar keeps track of file transfers
• should this be relevant, I am using NTFS hardlinks in the destination folder for deduplication

Edit: on my test it was 0.9.26040 and not 0.9.25070

[Alex4SSB]

@ilgrank Thanks for your input. What about transferring a single large file - is the speed reduced as well? Also, is WiFi connection any different?

[ilgrank]

thanks for the quick reply @Alex4SSB
I don't have the option to connect via WiFi at the moment, I'll try to replicate the setup on a notebook as soon as I can get my hands on one.
While I was at it tho, I have tried other comparisons:

• pressing CTRL+A to select all the (38200) files, takes significantly longer on 1.x. I think this happens partly because of ADB becoming unresponsive:

...but the interface also seems to handle such a large number of files being selected less efficiently than 0.9x, as every click operation while a large number of files is selected causes the main window to hang:

transfering a single large file happens at around 39Mb/s on 0.9x,

and 4x as fast on 1.x:

enumerating the 32800 files takes roughly the same time: 0.9x: 19.58s, on 1.0x 19.72s

[ilgrank]

Update: more tests on 1.x, and it seems that the large number of files being enumerated and hanging the main explorer window was the culprit.
Just copying the folder with 38K files without opening it does NOT freeze ADB Exporer nor ADB.
However, I get absymal speeds on such small-ish (around 4mb each) files:

Checking disk access with performance monitor, I see several parallel writes at around 65Kb/s, totalling around 1Mb/s

Using FTP, I usually ignore files with same date/size when merging, but it does not seem to be the case with ADB Explored, and instead each one of the files gets copied, even it it is already present on the target folder being merged.

[Alex4SSB]

Thanks again.

• I knew that the new method allows faster transfers but 170Mbps compared to 39 with pure ADB is new to me - ADB is supposed to be able to utilize USB3 speeds.
• It seems to me that what happened is that your transfer chokes the system (or one of the links in the chain). Still, it is weird, since a strong CPU, NVMe, and USB shouldn't limit these simultaneous operations.
• I will look into limiting the number of simultaneous operations to try to combat this.
• Can also try transferring 100 small files to see what speed you get?
• WiFi is usually faster than USB2 but that's not your case, but still might wanna try it just to be sure.
• 65K (2¹⁶) is the transfer chunk size by the way.

[ilgrank]

Hello Alex
I see you have assigned the "Fixed" tag to this issue, without closing it. May you please link the PR that fixed it or? Many thanks

EDIT: Sorry, I found it in the release notes

[Alex4SSB]

The latest version - 1.0.26080 should fix this, I didn't close the issue since I can't confirm the fix myself.

There is now a max simultaneous operations setting - you can perform your transfers and adjust the number if needed. If that solves the problem, I'll close the issue.