If I had only 20ms of latency I would not mind. However if multiple enet_host_service needs to be called to receive the full 3mb of data, then yes it starts to be noticeable. That is what I am wondering.

On 4/30/2013 9:16 AM, Doug Warren wrote:
enet_host_service has a built in timeout if no packets are received. By only calling it every 20ms you are introducing a fair amount of latency into the processing of the packets. What I had best luck doing is running it enet on a background thread with an incoming/outgoing queue of messages to/from the main threads with a 10ms timeout in enet_host_service, something like:
static int SERVER_UPDATE_TIMER = 10;
while (!_serverClosed && ((result = enet_host_service(_enetHost, &event, SERVER_UPDATE_TIMER)) >= 0))


{
        // Process event
        ...
        // Process outgoing events
        while(outgoingQueue.getNext(outEvent))
        {
            ...
        }
    }


On Tue, Apr 30, 2013 at 5:29 AM, Sebastien Robillard <[email protected] <mailto:[email protected]>> wrote:

    I am using enet 1.3.3 and I have an issue that might be related to
    enet. I am sending a reliable packet of about 3.5 mb over a local
    network and it takes approximately 8 seconds to receive it, which
    I believe should be much faster. I have a few questions on how
    enet handles these packets.

    1. Do the frequency of the call to enet_host_service (on either
    the sender or receiver end) matters for the time it takes to
    transfer the packet ?
    2. If so, would it change something if I call enet_host_service
    with a timeout ? Currently I have a timeout of 0, and move on if
    there are no events. enet_host_service is called every frame (~20 ms)
    3. Can we play with packet or buffer sizes in the enet library to
    improve the speed in my specific case ? I'm looking at defines
    like ENET_HOST_RECEIVE_BUFFER_SIZE or ENET_HOST_SEND_BUFFER_SIZE

    Thanks,
    Sebastien
    _______________________________________________
    ENet-discuss mailing list
    [email protected] <mailto:[email protected]>
    http://lists.cubik.org/mailman/listinfo/enet-discuss




_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss

_______________________________________________
ENet-discuss mailing list
[email protected]
http://lists.cubik.org/mailman/listinfo/enet-discuss

Reply via email to