Connections limit in 1.6.7.0 vs 0.9.60.2
Posted: 2023-03-31 04:32
I have just migrated from 0.9.60.2 to 1.6.7.0 and stumbled into problems with amount of connections to the server.
In 0.9.60.2 the amount of clients which can connect til FileZilla Server is "unlimited" by default
In 1.6.7.0 there seems to be a limit of maximum 10 connections.
I managed to raise this limit to 256 connections by changing the parameter "Number of threads" in Protocol settings -> Performance.
According to parameter 256 is the maximum limit that can be entered.
However I found this a bit misleading;
In 0.9.60.2 "Number of threads" represented how many CPU ressources the application could occupy, in 1.6.7.0 there is no balloon help text explaining the meaning of this parameter, and maybe I am just too simple a person that feels "Number of threads" is not a text I would link to max amount of connections.
Anywho, is this limit a new feature in FileZilla Server, a bug in the release and is there any method where I ran raise this limit beyond 256 which is the current maximum.
In 0.9.60.2 the amount of clients which can connect til FileZilla Server is "unlimited" by default
In 1.6.7.0 there seems to be a limit of maximum 10 connections.
I managed to raise this limit to 256 connections by changing the parameter "Number of threads" in Protocol settings -> Performance.
According to parameter 256 is the maximum limit that can be entered.
However I found this a bit misleading;
In 0.9.60.2 "Number of threads" represented how many CPU ressources the application could occupy, in 1.6.7.0 there is no balloon help text explaining the meaning of this parameter, and maybe I am just too simple a person that feels "Number of threads" is not a text I would link to max amount of connections.
Anywho, is this limit a new feature in FileZilla Server, a bug in the release and is there any method where I ran raise this limit beyond 256 which is the current maximum.