[ENet-discuss] Unreliable send optimisation

[Tim Auld]

When you send an unreliable message, Enet will allocate some memory, put it in the outgoing command list, and wait until an enet_host_service() call is made, right?  Is this for the benefit of throttling?  In the case where there is no throttling, waiting until an enet_host_service() call is made can cost several milliseconds in latency, not to mention some load in memory allocation and fragmentation.  A small degredation in performance has been noticed on local networks since Enet has been integrated.  Pings are generally higher, including some 10ms pings, which is unusual.  Is it possible to have an interface to send the message immediately?

Side note: I'm not too keen on the heavy run-time memory allocation.  It would be nice to have some options for pre-allocating an array of buffers.


Tim Auld
Lead Programmer
Ratbag 
Level 8, 63 Pirie Street, Adelaide SA 5000, Australia
Ph 08 8223 5830, Fax 08 8223 5746, Mobile 0413 660 994
email  tim at ratbaggames.com
Website  www.ratbaggames.com
 
This email is confidential for the addresse only and is subject to
copyright where applicable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.puremagic.com/pipermail/enet-discuss/attachments/20040211/afd8da6d/attachment.htm