Hello.
I am currently testing the FileZilla Server (ver1.4.0-rc1).
I am a beginner.
Please forgive my lack of study.
This time, I have three questions about Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
Please see attached file.
Question1:
What does mean the Number of threads item ?
Should I set this item?
Question2:
FileZilla Server (Ver1.4.0-rc1) has a "Performance" tab. There are "receive" and "send" items in this.
For example, does "receive" mean that FileZilla Server receives data from the client?
Also, does "send" mean that FileZilla Server sends data to the client?
Question3:
In FileZilla Server (Ver1.4.0-rc1), I'm wondering whether to change the "receive" and "send" items on the "Performance" tab.
I am testing by changing the value of "receive" and "send", but sometimes it is faster only at the beginning and slower in the middle (For example, when I set both "receive" and "send" item to 1024 KiB).
Therefore, I have not yet decided on the best setting.
I want to increase the transfer speed, but is it okay to keep the default like the attached file?
I am worried what to do because there is also the following post.
viewtopic.php?f=6&t=54426
Please give me advice.
About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
Moderator: Project members
About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
- Attachments
-
- picture.png (17.9 KiB) Viewed 2401 times
Re: About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
The number of threads controls on how many worker threads the load is distributed.
For optimal performance, TCP's receive window size needs to be at least as large as the bandwidth-delay product. Ideally, FileZilla Server would let you specify your network's BDP and configure the window size directly, but unfortunately the socket API lacks a way to control the window directly. It can be indirectly controlled though through the socket buffer sizes, at the expense of memory usage. The buffer sizes also affect the TCP window scale factor, but sadly on some systems, even setting insanely huge buffers restults in a window scale smaller than if no buffer sizes were explicitly configured.
Long story short: There is no perfect solution. Try and test which values fit best for your use-case.
For optimal performance, TCP's receive window size needs to be at least as large as the bandwidth-delay product. Ideally, FileZilla Server would let you specify your network's BDP and configure the window size directly, but unfortunately the socket API lacks a way to control the window directly. It can be indirectly controlled though through the socket buffer sizes, at the expense of memory usage. The buffer sizes also affect the TCP window scale factor, but sadly on some systems, even setting insanely huge buffers restults in a window scale smaller than if no buffer sizes were explicitly configured.
Long story short: There is no perfect solution. Try and test which values fit best for your use-case.
Re: About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
Thank you for reply.
Thank you , Mr.Kosse.
I understand very well.
Thank you , Mr.Kosse.
I understand very well.
Re: About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
I'm sorry , Mr.Kosse.
I have adittional question.
Is it okay that the value of "Number of threads:" is "0" like attached file?
I have adittional question.
Is it okay that the value of "Number of threads:" is "0" like attached file?
Re: About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
Yes. It means no worker thread is used, sessions are directly handled in the server's main thread.
Re: About Performance item of Protocols settings of FileZilla Server(ver1.4.0-rc1)
Thank you for reply.
Thank you , Mr.Kosse.
I understand very well.
Thank you , Mr.Kosse.
I understand very well.