3 ms·
IDK what SPECjbb does, but it really sort of depends on a lot of factors around how the JVM was setup. The JVM CAN be fairly cache friendly in the case where a
by cogman10 5y ago
IDK what SPECjbb does, but it really sort of depends on a lot of factors around how the JVM was setup.
The JVM CAN be fairly cache friendly in the case where allocations are used relatively close to one another. The JVM will (typically) keep memory allocated at the same time in roughly the same memory region.
- dragontamer 5y agohttps://www.spec.org/jbb2015/docs/designdocument.pdf https://www.spec.org/jbb2015/docs/designdocument.pdf SPECjbb is a large, Java benchmark. The idea is to create a "realistic enterprise system", and then measure the number of requests before 100ms latency is violated (aka: critical-jOPs), as well as maximum throughput (aka: max-jOPs). The general model is on a hypothetical Supermarket: each time a POS system scans things, the Headquarters has to double-check the status of coupons, report back to the POS system and determine if coupons are still valid. These hypothetical messages are GZipped XML that's getting passed back and forth between distinct JVMs, across the Grizzly-based non-blocking HTTPS server (default). The benchmark artificially shoves more-and-more requests through the system until the 100ms response time is violated (ex: the system is beginning to show signs of being overburdened). Then it continues to shove more data into the system until the maximum throughput is measured. It involves many JVMs doing many different tasks and communicating over Java-APIs. Thread pools, IPC, sockets, XML, HTTPS, encryption, the whole shebang.