You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have some features that need tags to be bigger than 65 bytes. Currently I forked your code and make it 255, then compiled and reinstalled
Can we make that value configurable? And what are the cons for that? From my side, I see only UDP buffer sizes will be impacted, it needs to be monitored and increased to prevent losing packets.
The text was updated successfully, but these errors were encountered:
You've just increased memory usage 4x for every tag.
That might affect overall memory usage quite seriuosly when there are millions of timers with tags.
I'll think about a way of making it configurable, but I can't think of any real need to send values this big. These are just tags, more or less unique identifiers, you really don't need to put whole poems in there.
Let me guess, you just use Namespace+Class name+Method as your tags, right? :)
Hi, I have some features that need tags to be bigger than 65 bytes. Currently I forked your code and make it 255, then compiled and reinstalled
Can we make that value configurable? And what are the cons for that? From my side, I see only UDP buffer sizes will be impacted, it needs to be monitored and increased to prevent losing packets.
The text was updated successfully, but these errors were encountered: