Home Forums Support about fileStream.Seek (..)

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #4018

    Hi MarcF

    In the File transfer Demo.When receiving file,there is some code like fileStream.Seek(..).

    This will ensure that the data is written to the appropriate location。

    If it is removed, there will be an error.

    But I think this may be cause performance problems.

    you know that Tcp Is transmitted in sequence.

    But at the time of receiving,The customThreadPool will Upset order。

    Make it necessary for us to use fileStream.Seek(..)

    Is there a good idea to help solve this problem?

    sorry for my poor english



    Heya msdc123,
    You are correct, there is a compromise here in terms of features vs performance. We found that for typical network bandwidths, ~1Gbps, the performance loss was minimal, particularly if using SSDs. To date we have been unable to find an implementation that removes this minor bottleneck, without the loss of significant features.

    Thanks for getting in touch,

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.