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 y'all! I'd open a PR for this, but I'm genuinely unsure as to what the meaning of the last sentence of this paragraph, taken from the README, is supposed to be:
You will get the best performance with the in-memory manager. The SQL adapters perform about 1000:1 compared to the in-memory solution. Please note that these tests where in laboratory environments with Docker, without an SSD, and single-threaded. You might get better results on your system. We are thinking about introducing It would be possible a simple cache strategy such as LRU with a maximum age to further reduce runtime complexity.
The text was updated successfully, but these errors were encountered:
You will get the best performance with the in-memory manager. The SQL adapters perform about 1000:1 compared to the in-memory solution. Please note that these tests where in laboratory environments with Docker, without an SSD, and single-threaded. You might get better results on your system. We are thinking about introducing other matching strategies (e.g. wildcard instead of regex) and also introducing simple cache strategies such as LRU with a maximum age to further reduce runtime complexity.
Hi y'all! I'd open a PR for this, but I'm genuinely unsure as to what the meaning of the last sentence of this paragraph, taken from the README, is supposed to be:
The text was updated successfully, but these errors were encountered: