Skip to content

Roadmap

Ben Manes edited this page Oct 6, 2015 · 135 revisions

Current

  • Allow hot reads to skip maintenance work (maybe 2-3x speedup?)

Version 2.0

A major revision that includes API incompatible changes.

  • DONE: Replace LRU with W-TinyLfu eviction policy
  • RemovalListener
    • Use friendlier typed lambda syntax to chain as (k, v, cause) -> ...
    • RemovalNotification retained as helper, but not used in the API
  • AsyncLocalCache
    • Consider extending Cache<K, CompletableFuture<V>> interface
      • Cache: Conflict on get(k, k -> v) with get(k, k -> future)
      • LoadingCache: Conflicts on getAll returning future<map> vs map<k, future>
    • Add asMap() view of key -> future
  • Stats
    • Show disabled stats via a new flag on CacheStats
  • Tracing
    • This package may be removed entirely after integrating a optimal replacement policy
  • CacheLoader
    • Revisit having loads throw checked exceptions (forgot why it was decided against)
    • Should rethrow a checked exception as a CompletionException (document)
  • JCache
    • Rename CopyStrategy to Copier
  • Misc
    • Remove NonReentrantLock (embed usage)
    • Consider removal of UnsafeAccess (or wait until VarHandles rewrite?)
    • Review ConcurrentLinkedStack for promotion out of Beta status
    • Explore better fork-join scheduling for maintenance ("chewing up threads")
      • This only happened on a synthetic load test so FJ was thrashing
      • To combat that, our benchmarks use a single-threaded FJ pool
      • A little smarter scheduling should resolve this quirk
    • Document asMap view supports atomic versions of the compute methods

Future

  • Collections
  • Simulator
    • Add weight and expiration support
  • Consider encoding the linked lists as arrays
    • 64-bit reference becomes 32-bit int (only if compressed OOPS is not enabled)
    • Better caching effects due to contiguous data
    • Cons: Limits the size (2B entries), cost is minimal due to maintenance done using ForkJoinPool
  • Benchmark arena spacing vs padding for better false sharing avoidance

Clone this wiki locally