>
> Do ESI users want to trade speed for memory savings? What memory savings
> and speed reduction do you anticipate for a typical use case or two?
>
> In light of the fact that it's only used by ESI, I think it's not
worthwhile investing in it.
___
On 6/19/20 5:13 PM, Francesco Chemolli wrote:
> I'm looking at the TrieNode code, and while it's super fast, it's
> quite memory-hungry: each node uses 2kb of RAM for the children index
> and any moderately-sized Trie has plenty of nodes. On the upside, it's
> blazing fast.
In Squid, TrieNode
On 20/06/20 9:13 am, Francesco Chemolli wrote:
> Hi all,
> I'm looking at the TrieNode code, and while it's super fast, it's
> quite memory-hungry: each node uses 2kb of RAM for the children index
> and any moderately-sized Trie has plenty of nodes. On the upside, it's
> blazing fast.
>
> How
