Using MapDB could significantly improve startup performance compared with Chronicle Map for the CLI. Chronicle Map has a high initialization cost, since we start a new JVM for each run.
While the maximum throughput of MapDB is reportedly not quite as high as Chronicle Map, it provides much faster startup times, typically in the range of a few milliseconds as opposed to hundreds of milliseconds, because it avoids heavy off-heap memory allocation and large pre-initialized structures. In general, it seems better suited for short-lived processes.
Using MapDB could significantly improve startup performance compared with Chronicle Map for the CLI. Chronicle Map has a high initialization cost, since we start a new JVM for each run.
While the maximum throughput of MapDB is reportedly not quite as high as Chronicle Map, it provides much faster startup times, typically in the range of a few milliseconds as opposed to hundreds of milliseconds, because it avoids heavy off-heap memory allocation and large pre-initialized structures. In general, it seems better suited for short-lived processes.