<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I was under the impression ENet handled packets larger than the MTU
on both reliable and unreliable.<br>
Just to make sure I understand: So this is only the case for
reliable packets?<br>
<br>
Thanks,<br>
Stefan<br>
<br>
On 2012-10-02 15:25, Lee Salzman wrote:
<blockquote
cite="mid:CAPk1TVGRHvKw6aC8UudpuUsv7W4579B=OR+TYSx5pbXGHR6=jA@mail.gmail.com"
type="cite">Sending a lot of little ENet packets (10-20 bytes) is
going to consume a lot more than that per packet in terms of
internal ENet protocol headers. To save on header overhead, you
should batch stuff together into one bigger packet on your end,
especially if it is reliable. If it is unreliable, you should
still batch, but make sure you're not going over the MTU, and if
so, either using unreliable fragment, or making sure to split
stuff up so to not accidentally get packets marked reliable that
you don't want.<br>
<br>
<div class="gmail_quote">On Tue, Oct 2, 2012 at 4:20 PM, Lucas
Beyer <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pompei2@gmail.com" target="_blank">pompei2@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
My gameserver runs in ticks (0.1-0.01s). Each tick, events
happen,<br>
which need to be reliably sent to the clients.<br>
<br>
Is it better to<br>
a) each tick, send one big message containing all events which<br>
happened during the tick or<br>
b) send each event (~10-20 bytes) as a separate message during
the tick?<br>
<br>
As I understood, messages are only really sent through the
wire during<br>
a call to enet_host_service, right? I call this between two
ticks, so<br>
in both cases a) and b) would send the message(s) at the end
of the<br>
tick.<br>
<br>
I know the best answer is "implement both then measure" but I
was<br>
wondering if, in enet and considering they all need to be
reliable<br>
messages, there are reasons why one might be inherently better
than<br>
the other. "big" is around 10-20 kilobytes.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Best regards, Lucas<br>
<a moz-do-not-send="true" href="http://arkana-fts.org"
target="_blank">http://arkana-fts.org</a><br>
_______________________________________________<br>
ENet-discuss mailing list<br>
<a moz-do-not-send="true"
href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a><br>
<a moz-do-not-send="true"
href="http://lists.cubik.org/mailman/listinfo/enet-discuss"
target="_blank">http://lists.cubik.org/mailman/listinfo/enet-discuss</a><br>
</font></span></blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ENet-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ENet-discuss@cubik.org">ENet-discuss@cubik.org</a>
<a class="moz-txt-link-freetext" href="http://lists.cubik.org/mailman/listinfo/enet-discuss">http://lists.cubik.org/mailman/listinfo/enet-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>