Kelvin Nilsen

In this mode, transactions never have to wait on updates to shared data base. Instead, a new background thread repeatedly rebuilds the data bases from change logs, then replaces the...

Revise tests to avoid this dependency as jdk.nashorn is no longer bundled with most current OpenJDK releases.

As currently implemented, Extremem is best suited to modeling of application services that are running in steady state mode (allocating temporary objects at roughly the same pace they are discarding...

For a given JVM garbage collector and Extremem workload configuration, it is desirable to automate the exploration of what range of JVM configurations (e.g. how many cores, how much heap...

Scripts to automate the running of Extremem and especially the assimilation of output reports would be very helpful. This would facilitate use of Extremem to support performance and latency regression...

As more developers contribute to the implementation of Extremem, it is desirable to establish a suite of test programs and a framework for applying a regression test suite on the...

The configuration options of Extremem are designed to allow Extremem to mimic the memory workload behavior of broad varieties of real-world applications and services. These workloads are typically characterized in...

Part of the computational workload shouldered by Extremem is to track the total allocations performed by each thread along with tracking when previously allocated objects should become eligible for garbage...

The version and build number should be written to standard output with the reporting of other configuration information. Adding this information to the output helps make comparison of results between...

The goal is to simplify capture, sharing, and repetition of workload configurations between different runs.