New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

dw-cache

Package Overview
Dependencies
Maintainers
1
Versions
121
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

dw-cache

The highest performance constant complexity cache algorithm.

  • 0.0.102
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8
decreased by-74.19%
Maintainers
1
Weekly downloads
 
Created
Source

Dual Window Cache

CI

The highest performance constant complexity cache algorithm.

Maintenance

The source code is maintained on the next source repository.

https://github.com/falsandtru/spica

Strategies

  • Dynamic partition
  • Transitive wide MRU with cyclic replacement
  • Sampled history injection

Properties

Generally superior and almost flawless.

  • High performance
    • High hit ratio (DS1, S3, OLTP, GLI)
      • Highest hit ratio among all the general-purpose cache algorithms.
      • Near ARC (S3, OLTP).
      • Significantly higher than ARC (DS1, GLI).
    • Low overhead (High throughput)
      • Use of only two lists.
    • Low latency
      • Constant time complexity.
      • No batch processing like LIRS and TinyLFU.
    • Parallel suitable
      • Separated lists are suitable for lock-free processing.
  • Efficient
    • Low memory usage
      • Constant extra space complexity.
      • Retain only keys of resident entries (No history).
    • Immediate release of evicted keys
      • Primary cache algorithm in the standard library must release memory immediately.
  • High resistance
    • Scan, loop, and burst resistance
  • Few tradeoffs
    • Not the highest hit ratio
    • Very smaller cache size than sufficient can degrade hit ratio
  • Upward compatible with ARC
    • Comprehensively higher performance
  • Upward compatible with Segmented LRU
    • Totally higher performance
    • Suitable for TinyLFU
      • Better for (W-)TinyLFU's eviction algorithm.

Efficiency

Some different cache algorithms require extra memory space to retain evicted keys. Linear time complexity indicates the existence of batch processing. Note that admission algorithm doesn't work without eviction algorithm.

AlgorithmTypeTime complexity
(Worst case)
Space complexity
(Extra)
Key sizeData structures
LRUEvictConstantConstant1x1 list
DWCEvictConstantConstant1x2 lists
ARCEvictConstantLinear2x4 lists
LIRSEvictLinearLinear3-2500x2 lists
TinyLFUAdmitLinearLinear~1-10x
(8bit * 10N * 4)
5 arrays
W-TinyLFUAdmitLinearLinear~1-10x
(8bit * 10N * 4)
1 list
4 arrays

https://github.com/ben-manes/caffeine/wiki/Efficiency
https://github.com/zhongch4g/LIRS2/blob/master/src/replace_lirs_base.cc

Resistance

LIRS's burst resistance means resistance to continuous cache misses.

AlgorithmTypeScanLoopBurst
LRUEvict
DWCEvict
ARCEvict
LIRSEvict
TinyLFUAdmit
W-TinyLFUAdmit

Tradeoffs

Note that LIRS and TinyLFU are risky cache algorithms.

  • LRU
    • Low performance
    • No resistance
      • Scan access clears all entries.
  • DWC
    • Not the highest hit ratio
    • Very smaller cache size than sufficient can degrade hit ratio
  • ARC
    • Middle performance
    • Inefficient
      • 2x key size.
    • High overhead
      • 4 lists.
    • Few resistance
      • No loop resistance.
  • LIRS
  • TinyLFU
    • Incomplete algorithm
      • Burst access degrades performance.
      • TinyLFU is worse than LRU in theory.
      • TinyLFU is just an incomplete implementation of W-TinyLFU.
    • High overhead
      • Read and write 40 array elements per access.
    • Restricted delete operation
      • Bloom filters don't support delete operation.
      • Frequent delete operations degrade performance.
    • Spike latency
      • Whole reset of Bloom filters takes linear time.
    • Vulnerable algorithm
      • Burst access saturates Bloom filters.
  • W-TinyLFU
    • High overhead
      • Read and write 40 array elements per access.
    • Restricted delete operation
      • Bloom filters don't support delete operation.
      • Frequent delete operations degrade performance.
    • Spike latency
      • Whole reset of Bloom filters takes linear time.

Hit ratio

Note that another cache algorithm sometimes changes the parameter values per workload to get a favorite result as the paper of TinyLFU has changed the window size of W-TinyLFU. All the results of DWC are measured by the same default parameter values. TinyLFU's results are traces of Ristretto. W-TinyLFU's results are traces of Caffeine.

  1. Set the datasets to ./benchmark/trace (See ./benchmark/ratio.ts).
  2. Run npm i
  3. Run npm run bench
  4. Click the DEBUG button to open a debug tab.
  5. Close the previous tab.
  6. Press F12 key to open devtools.
  7. Select the console tab.

https://github.com/dgraph-io/benchmarks
https://github.com/ben-manes/caffeine/wiki/Efficiency
https://github.com/dgraph-io/ristretto
https://docs.google.com/spreadsheets/d/1G3deNz1gJCoXBE2IuraUSwLE7H_EMn4Sn2GU0HTpI5Y
https://github.com/jedisct1/rust-arc-cache/issues/1

DS1

W-TinyLFU > DWC > (LIRS) > (TinyLFU) > ARC > LRU

  • DWC is an approximation of W-TinyLFU.

image

DS1 1,000,000
LRU hit ratio 3.08%
DWC hit ratio 11.77%
DWC - LRU hit ratio delta 8.69%
DWC / LRU hit ratio rate  381%

DS1 2,000,000
LRU hit ratio 10.74%
DWC hit ratio 28.48%
DWC - LRU hit ratio delta 17.74%
DWC / LRU hit ratio rate  265%

DS1 3,000,000
LRU hit ratio 18.59%
DWC hit ratio 39.11%
DWC - LRU hit ratio delta 20.52%
DWC / LRU hit ratio rate  210%

DS1 4,000,000
LRU hit ratio 20.24%
DWC hit ratio 44.71%
DWC - LRU hit ratio delta 24.46%
DWC / LRU hit ratio rate  220%

DS1 5,000,000
LRU hit ratio 21.03%
DWC hit ratio 51.39%
DWC - LRU hit ratio delta 30.35%
DWC / LRU hit ratio rate  244%

DS1 6,000,000
LRU hit ratio 33.95%
DWC hit ratio 57.64%
DWC - LRU hit ratio delta 23.68%
DWC / LRU hit ratio rate  169%

DS1 7,000,000
LRU hit ratio 38.89%
DWC hit ratio 62.30%
DWC - LRU hit ratio delta 23.40%
DWC / LRU hit ratio rate  160%

DS1 8,000,000
LRU hit ratio 43.03%
DWC hit ratio 68.83%
DWC - LRU hit ratio delta 25.79%
DWC / LRU hit ratio rate  159%

S3

W-TinyLFU > (TinyLFU) > (LIRS) > DWC, ARC > LRU

  • DWC is an approximation of ARC.

image

S3 100,000
LRU hit ratio 2.32%
DWC hit ratio 10.60%
DWC - LRU hit ratio delta 8.27%
DWC / LRU hit ratio rate  455%

S3 200,000
LRU hit ratio 4.63%
DWC hit ratio 19.01%
DWC - LRU hit ratio delta 14.38%
DWC / LRU hit ratio rate  410%

S3 300,000
LRU hit ratio 7.58%
DWC hit ratio 25.06%
DWC - LRU hit ratio delta 17.47%
DWC / LRU hit ratio rate  330%

S3 400,000
LRU hit ratio 12.03%
DWC hit ratio 30.42%
DWC - LRU hit ratio delta 18.38%
DWC / LRU hit ratio rate  252%

S3 500,000
LRU hit ratio 22.76%
DWC hit ratio 38.05%
DWC - LRU hit ratio delta 15.28%
DWC / LRU hit ratio rate  167%

S3 600,000
LRU hit ratio 34.63%
DWC hit ratio 46.81%
DWC - LRU hit ratio delta 12.18%
DWC / LRU hit ratio rate  135%

S3 700,000
LRU hit ratio 46.04%
DWC hit ratio 55.70%
DWC - LRU hit ratio delta 9.66%
DWC / LRU hit ratio rate  120%

S3 800,000
LRU hit ratio 56.59%
DWC hit ratio 64.04%
DWC - LRU hit ratio delta 7.44%
DWC / LRU hit ratio rate  113%

OLTP

W-TinyLFU > ARC > DWC > (LIRS) > LRU > (TinyLFU)

  • DWC is an approximation of ARC.

image

OLTP 250
LRU hit ratio 16.47%
DWC hit ratio 19.36%
DWC - LRU hit ratio delta 2.88%
DWC / LRU hit ratio rate  117%

OLTP 500
LRU hit ratio 23.44%
DWC hit ratio 27.92%
DWC - LRU hit ratio delta 4.48%
DWC / LRU hit ratio rate  119%

OLTP 750
LRU hit ratio 28.28%
DWC hit ratio 33.54%
DWC - LRU hit ratio delta 5.26%
DWC / LRU hit ratio rate  118%

OLTP 1,000
LRU hit ratio 32.83%
DWC hit ratio 37.52%
DWC - LRU hit ratio delta 4.69%
DWC / LRU hit ratio rate  114%

OLTP 1,250
LRU hit ratio 36.20%
DWC hit ratio 39.63%
DWC - LRU hit ratio delta 3.42%
DWC / LRU hit ratio rate  109%

OLTP 1,500
LRU hit ratio 38.69%
DWC hit ratio 41.40%
DWC - LRU hit ratio delta 2.71%
DWC / LRU hit ratio rate  107%

OLTP 1,750
LRU hit ratio 40.78%
DWC hit ratio 43.00%
DWC - LRU hit ratio delta 2.21%
DWC / LRU hit ratio rate  105%

OLTP 2,000
LRU hit ratio 42.46%
DWC hit ratio 44.27%
DWC - LRU hit ratio delta 1.80%
DWC / LRU hit ratio rate  104%

GLI

W-TinyLFU, (LIRS) > DWC > (TinyLFU) >> ARC > LRU

  • DWC is an approximation of W-TinyLFU.

image

GLI 250
LRU hit ratio 0.93%
DWC hit ratio 16.25%
DWC - LRU hit ratio delta 15.32%
DWC / LRU hit ratio rate  1746%

GLI 500
LRU hit ratio 0.96%
DWC hit ratio 32.76%
DWC - LRU hit ratio delta 31.79%
DWC / LRU hit ratio rate  3398%

GLI 750
LRU hit ratio 1.16%
DWC hit ratio 41.32%
DWC - LRU hit ratio delta 40.15%
DWC / LRU hit ratio rate  3551%

GLI 1,000
LRU hit ratio 11.22%
DWC hit ratio 49.61%
DWC - LRU hit ratio delta 38.39%
DWC / LRU hit ratio rate  442%

GLI 1,250
LRU hit ratio 21.25%
DWC hit ratio 52.62%
DWC - LRU hit ratio delta 31.36%
DWC / LRU hit ratio rate  247%

GLI 1,500
LRU hit ratio 36.56%
DWC hit ratio 53.78%
DWC - LRU hit ratio delta 17.22%
DWC / LRU hit ratio rate  147%

GLI 1,750
LRU hit ratio 45.04%
DWC hit ratio 55.66%
DWC - LRU hit ratio delta 10.62%
DWC / LRU hit ratio rate  123%

GLI 2,000
LRU hit ratio 57.41%
DWC hit ratio 57.96%
DWC - LRU hit ratio delta 0.54%
DWC / LRU hit ratio rate  100%

Throughput

80-120% of lru-cache.

Note that the number of trials per capacity for simulation 1,000,000 is insufficient.

No result with 10,000,000 because lru-cache crushes with the next error on the next machine of GitHub Actions. It is verified that the error was thrown also when benchmarking only lru-cache. Of course it is verified that DWC works fine under the same condition.

Error: Uncaught RangeError: Map maximum size exceeded

System:
OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
CPU: (2) x64 Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
Memory: 5.88 GB / 6.78 GB

Clock: spica/clock
ISCCache: lru-cache
LRUCache: spica/lru
DW-Cache: spica/cache

'Clock    new x 1,328,833 ops/sec ±3.63% (113 runs sampled)'

'ISCCache new x 13,768 ops/sec ±1.00% (120 runs sampled)'

'LRUCache new x 27,168,783 ops/sec ±1.50% (122 runs sampled)'

'DW-Cache new x 6,049,201 ops/sec ±0.86% (122 runs sampled)'

'Clock    simulation 100 x 13,493,137 ops/sec ±1.65% (121 runs sampled)'

'ISCCache simulation 100 x 8,651,793 ops/sec ±1.85% (121 runs sampled)'

'LRUCache simulation 100 x 10,604,646 ops/sec ±2.24% (120 runs sampled)'

'DW-Cache simulation 100 x 7,242,013 ops/sec ±1.65% (121 runs sampled)'

'Clock    simulation 1,000 x 10,694,963 ops/sec ±1.81% (120 runs sampled)'

'ISCCache simulation 1,000 x 7,700,019 ops/sec ±1.90% (121 runs sampled)'

'LRUCache simulation 1,000 x 9,184,813 ops/sec ±2.13% (120 runs sampled)'

'DW-Cache simulation 1,000 x 7,041,470 ops/sec ±1.77% (120 runs sampled)'

'Clock    simulation 10,000 x 10,517,215 ops/sec ±1.78% (122 runs sampled)'

'ISCCache simulation 10,000 x 7,365,593 ops/sec ±1.67% (121 runs sampled)'

'LRUCache simulation 10,000 x 8,685,666 ops/sec ±1.81% (121 runs sampled)'

'DW-Cache simulation 10,000 x 7,317,621 ops/sec ±1.42% (120 runs sampled)'

'Clock    simulation 100,000 x 7,417,826 ops/sec ±1.60% (118 runs sampled)'

'ISCCache simulation 100,000 x 4,523,157 ops/sec ±1.22% (117 runs sampled)'

'LRUCache simulation 100,000 x 5,424,344 ops/sec ±2.10% (119 runs sampled)'

'DW-Cache simulation 100,000 x 4,190,537 ops/sec ±1.44% (113 runs sampled)'

'Clock    simulation 1,000,000 x 4,519,623 ops/sec ±3.63% (106 runs sampled)'

'ISCCache simulation 1,000,000 x 2,081,961 ops/sec ±3.35% (101 runs sampled)'

'LRUCache simulation 1,000,000 x 2,686,808 ops/sec ±3.88% (103 runs sampled)'

'DW-Cache simulation 1,000,000 x 2,481,012 ops/sec ±2.54% (111 runs sampled)'
const key = random() < 0.9
  ? random() * capacity * 1 | 0
  : random() * capacity * 9 + capacity | 0;
cache.get(key) ?? cache.set(key, {});

Comprehensive evaluation

Hit ratio

ClassAlgorithms
Very highW-TinyLFU
HighDWC, (LIRS)
MiddleARC, (TinyLFU)
LowLRU

Efficiency

Extra spaceAlgorithms
ConstantLRU, DWC
Linear (< 1)W-TinyLFU > (TinyLFU)
Linear (1)ARC
Linear (> 1)(LIRS)

Resistance

ClassEffectAlgorithms
TotalHighW-TinyLFU, DWC
MostHigh(TinyLFU), (LIRS)
FewLowARC
NoneNoneLRU

Throughput

ClassAlgorithms
Dynamic lists (Lock-free)DWC > (LIRS) > ARC
Bloom filter + Dynamic lists(TinyLFU)
Dynamic lists + Bloom filterW-TinyLFU
Static listLRU

Latency

TimeAlgorithms
ConstantLRU, DWC, ARC
Linear (1)W-TinyLFU > (TinyLFU)
Linear (> 1)(LIRS)

Vulnerability

ClassAlgorithms
Degrade(TinyLFU)
Crush(LIRS)

API

export namespace Cache {
  export interface Options<K, V = undefined> {
    // Max entries.
    // Range: 1-
    readonly capacity?: number;
    // Max costs.
    // Range: L-
    readonly resource?: number;
    readonly age?: number;
    readonly eagerExpiration?: boolean;
    // WARNING: Don't add any new key in disposing.
    readonly disposer?: (value: V, key: K) => void;
    readonly capture?: {
      readonly delete?: boolean;
      readonly clear?: boolean;
    };
    // Mainly for experiments.
    // Min LRU ratio.
    // Range: 0-100
    readonly window?: number;
    // Sample ratio of LRU in LFU.
    // Range: 0-100
    readonly sample?: number;
    readonly sweep?: {
      readonly threshold?: number;
      readonly ratio?: number;
      readonly window?: number;
      readonly room?: number;
      readonly range?: number;
      readonly shift?: number;
    };
  }
}
export class Cache<K, V> {
  constructor(capacity: number, opts?: Cache.Options<K, V>);
  constructor(opts: Cache.Options<K, V>);
  add(key: K, value: V, opts?: { size?: number; age?: number; }): boolean;
  add(this: Cache<K, undefined>, key: K, value?: V, opts?: { size?: number; age?: number; }): boolean;
  put(key: K, value: V, opts?: { size?: number; age?: number; }): boolean;
  put(this: Cache<K, undefined>, key: K, value?: V, opts?: { size?: number; age?: number; }): boolean;
  set(key: K, value: V, opts?: { size?: number; age?: number; }): this;
  set(this: Cache<K, undefined>, key: K, value?: V, opts?: { size?: number; age?: number; }): this;
  get(key: K): V | undefined;
  has(key: K): boolean;
  delete(key: K): boolean;
  clear(): void;
  resize(capacity: number, resource?: number): void;
  readonly length: number;
  readonly size: number;
  [Symbol.iterator](): Iterator<[K, V], undefined, undefined>;
}

Keywords

FAQs

Package last updated on 17 May 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc