Like comments, this is most likely not the transfer rate causing the problem, but rather serialization.
There are 3 things to consider:
- CPU usage for serialization and deserialization
- saving objects in memory
- transmission speed
To send 250 MB, it will first be serialized, then sent, then deserialized. This can lead to 3 copies of data in memory, which can lead to a disk break.
We had a similar problem a few years ago, and in the end I switched to calling the DLL directly, transferring the memory link to the list will take approx. 1 millisecond
source share