Opened 11 years ago
Last modified 10 years ago
#7909 new Bug report
Max Simultaneous Transfers over set limit causes server timeouts
|Reported by:||Barry Ira Geller||Owned by:|
|Component version:||Operating system type:||Windows|
|Operating system version:||winxp sp3|
In Concurrent Transfers default was 4 but Filezilla was trying to send more than 8 simultaneous transfers causing Server to do dozens of 5 second timeouts since it has a limit of 8 concurrent transfers allowed. Verified this was the problem in cPanel, which showed 8 current transfers, with warnings. This occurred when I was uploading about 2200 files. Left about 120 as "failed".
Basically, even though setting was 4 concurrent transfers, program was sending 8 and trying to do more, stalling out my server.
After complete, I changed the settings to 3 simultaneous transfers, put the failed files back into live queue and resent OK.
Conclusion: the amount of files in upload queue caused something to override default simultaneous setting.
Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2012-01-08
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions
Name: Windows XP (build 2600, Service Pack 3)
Platform: 32 bit system
Change History (1)
comment:1 by , 11 years ago
|Operating system type:||Linux → Windows|
After further testing, even with 500 or more files, the superspeed of the download just seems to push/override filezilla's cuncurrency setting right into the roof of the max streams available.