[ENet-discuss] speed up sending outgoing queue commands

[Pablo de Heras Ciechomski]

Hi Eric,

1) Speeding up reliable data

This is a very complex question to me at least. First of all good to
separate (incoming/outgoing) messages but I fail to understand the need of
a separate thread. Maybe you meant a incoming queue and an outgoing queue,
since there can only be one thread accessing ENet at a time (it's not
thread-safe). The speed isn't really determined by how fast or how often
you call enet_host_service since you seem to always be calling it (also
something that tells me that your message sending thread might be messing
things up - not thread-safe) but is dependent on how fast the receiver
sends back his acks.

2) No idea. What do you mean?

Best regards,

Pablo
-- 
////////////////////////////////////////////////////////////////
Dr.Sc. Pablo de Heras Ciechomski, founder
pablo at sciencevisuals.com
www.sciencevisuals.com

On Thu, Sep 24, 2015 at 3:06 AM, Eric <shunxung+enet at gmail.com> wrote:

>
> Hi all,
>
> 1.  I use a child thread to send many reliable packets in a short time and
> the main thread is the loop to call *enet_host_service* regularly(1000ms).
> But I found that most of packets are queued in *outgoingReliableCommands.
>  *I tried to use *enet_host_flush* in main thread but it seems unhelpful.
> How could I speed up sending *outgoingReliableCommands *(enet_host_service
> timeout?) or how could I check where the bottleneck is? (because of recv
> peer side?)
>
> 2. Is it possible to clear specific channel packet data?
>
>
> _______________________________________________
> ENet-discuss mailing list
> ENet-discuss at cubik.org
> http://lists.cubik.org/mailman/listinfo/enet-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cubik.org/pipermail/enet-discuss/attachments/20150924/9ecbdec3/attachment.html>