Try `seize` as a replacement of `crossbeam-epoch`? about moka HOT 3 OPEN

Unlike crossbeam-epoch, seize provides the followings:

1. Configurable batch_size: Collector::batch_size
   • This controls the tradeoff between throughput and memory efficiency.
   • Maybe moka cache should allow user to change this value when creating an instance of cache.
2. Protection against stalled threads: Collector::epoch_frequency
   • This ensures evicted cache entries to be eventually dropped.
3. No global collector:
   • Each moka cache instance will have a dedicated seize collector.
   • This ensures all cached entries to be dropped when the cache instance is dropped.

from moka.

I am doing some experiments in a separate repository.

• https://gitlab.com/moka-labs/moka-gh385-seize/moka
• Diff: a77b947f...cht-seize

from moka.

Memo:

Ideally, I want a concurrent memory reclamation library to provide the followings:

1. Give us a control whether this differed destruction request should be buffered in a thread local storage or not.
   • We want some of them not to be buffered, while others to be buffered.
2. Provide an API to trigger a GC.
3. When a GC runs, pull differed destruction requests from the local buffers of all registered threads,
   • instead of letting each threads to push them to the global queue.

from moka.