[ENet-discuss] Large data packets over ENet

[Lee Salzman]

If you try to use ENet like TCP (which you are), performance is going to 
suck. ENet
is simply not made to transfer large streams of bulk data as efficiently 
as possible, but
is instead optimized to transfer lots of little packets with as low 
latency as possible.
Totally different focus.

Lee

Jacco Bikker wrote:

> Couldn’t you look at the client-server model like this: The server is 
> the ‘managing’ system that distributes data to all clients. In that 
> case, it’s not strange to call the rendering system ‘server’. In fact, 
> this system will also handle user interaction and so on, so it’s 
> definitely the system that knows most about the process. Perhaps 
> ‘master-slave’ is better, like in OpenMPI.
>
> Data transfer rates: It’s 768KB raw data indeed, and it gets 
> compressed (using LZO) to about 1/6^th of that (lossless, there are 
> quite some black areas in the sample scene I’m using). That’s still 
> more than 100KB per frame, so at 20fps, it’s 2MB. The network should 
> be able to handle that, but ENet isn’t: Performance drops to 400ms per 
> frame where I achieved 200ms or less in the original application (no 
> client-server rendering), or 240 in my first (buggy) UDP/Winsock 
> implementation with LZO compression. For comparison: Last night I 
> tried RakNet, which manages to get 270ms frames (also using LZO 
> compression), which isn’t optimal, but pretty close.
>
> ------------------------------------------------------------------------
>
>     ------------------------------------------------------------------------
>