You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running two different network connections. One is over WIFI with 25MBit/s upload at 1% packet loss. One is over mobile with 24MBit/s upload at 0% packet loss. The first connection takes 10x as long to upload files to a Django server, while the mobile connection is a lot faster. This app is the only place where I'm experiencing slowdowns. I use this connection every day for everything else. As far as I can tell, Alamofire is the only part of the chain that could cause these slowdowns.
Alamofire is built on top of URLSession and so isn't responsible for any of its own networking. Uploads are handled by URLSession and the raw network connection, as well as the logic dealing with packet loss, are at an even lower level. So there's not much Alamofire can do to impact, or fix, raw network speed. I suggest you investigate further and try to find the bottleneck in your upload operation. One thing to investigate is whether moving away from multipart form uploads and directly uploading the file would improve performance.
I'm running two different network connections. One is over WIFI with 25MBit/s upload at 1% packet loss. One is over mobile with 24MBit/s upload at 0% packet loss. The first connection takes 10x as long to upload files to a Django server, while the mobile connection is a lot faster. This app is the only place where I'm experiencing slowdowns. I use this connection every day for everything else. As far as I can tell, Alamofire is the only part of the chain that could cause these slowdowns.
Alamofire Environment
Alamofire Version: 5.4.3
Dependency Manager: SPM
Xcode Version: 12.5.1
Swift Version: 5
Platform(s) Running Alamofire: iOS 14.6
macOS Version Running Xcode: 11.4
Demo Project
ℹ Please link to or upload a project we can download that reproduces the issue.
The text was updated successfully, but these errors were encountered: