Got it.
Mind if we talk through this a bit? I have a feeling you'll do okay
without UDP.
Are you looking at 1M sets + 1M gets/sec per memcached or for the whole
cluster?
UDP sets can't be multi-packet; it's not implemented at all. Jumbo frames
may help (I forget if the MTU is discovered
We haven't started tuning for UDP. That module was a PoC because all the
other memcache modules were _incomplete_ in terms of feature set. We use
namespaces for different things like threats, assets, users, containers,
etc. The plan is to also use pools to scale the memory and allow for easier
Hey,
That is exactly the use case I would expect out of UDP! Thanks for
responding so quickly.
In your example module I can't quickly figure out how UDP is configured
(it just seems to import dalli and use it?)
Are you using multi-packet responses for UDP lookups? If you're running
sets via UDP
I still have a use case for it. We're looking to make the highest
performing enrichment for log ingestion possible.
https://www.elastic.co/blog/elasticsearch-data-enrichment-with-logstash-a-few-security-examples
In the use case described above, we aim to enrich as close to real time as
possible
Not sure how active this list is anymore :P
Are any of you still listening users of the UDP protocol? If so, mind
reaching out to me (here or privately) to explain your use case?
I'm thinking around some long term options with it; one is to turn it into
a compile flag, and another is to keep it
