Bug 27152 - TCPClient performance concerns
Summary: TCPClient performance concerns
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mark Probst
Depends on:
Reported: 2015-02-17 13:10 UTC by Cody Beyer (MSFT)
Modified: 2015-03-06 16:56 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Comment 2 Vlad Brezae 2015-03-06 16:56:10 UTC

    I reproduced this issue but it doesn't appear to be caused by TcpClient, but by excessive allocation of large objects in ReadMessageWithLength (buffer). The different GC heuristics in mono vs java lead to the big difference in performance. The problem can be fixed by allocating the buffer to the exact size that you want to read from the socket.