3 ms·
Ok. So I guess it doesn't try to go very fast.
by fulafel 7mo ago
Ok. So I guess it doesn't try to go very fast.
- ajb 7mo agoBuffer size is the product of bandwidth and delay, so if communicating with something close, it can still go fast. Had an illustration of this once when my then-employers IT dept set up the desktop IP phones to update from a TFTP server on the other continental land mass. Since TFTP only allows one outstanding packet, everyone outside head office had to wait a long time for their phone to update, while head office didn't see any issue.
- sbrivio 7mo agopasst has been doing something similar for years (see https://passt.top/kvm_forum_2022.pdf https://passt.top/kvm_forum_2022.pdf pages 17, 18) and it's actually pretty fast (https://passt.top/#performance_1 https://passt.top/#performance_1), even though it's not as resource-constrained as WolfIP. We're finally adding multithreading (https://bugs.passt.top/show_bug.cgi?id=13 https://bugs.passt.top/show_bug.cgi?id=13) these days.
- pseudohadamard 7mo agoIf it's a memory-constrained embedded device you're sending a handful of bytes of telemetry every now and then, not aiming for gigabit speeds. In fact it couldn't get to megabit speeds even if it wanted to. For something like that this is perfect.