partial_run QEMU testing on Alpine Linux v3.20 3.20.2 via the Phoronix Test Suite. overnight with full access, 48gb memory: Processor: 2 x QEMU Virtual 2.5+ (32 Cores), Motherboard: QEMU Standard PC (i440FX + PIIX 1996) (rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org BIOS), Memory: 48GB, Disk: 34GB QEMU HDD, Graphics: bochs-drmdrmfb, Monitor: QEMU Monitor OS: Alpine Linux v3.20 3.20.2, Kernel: 6.6.44-0-virt (x86_64), Compiler: GCC 13.2.1 20240309, File-System: ext4, Screen Resolution: 1280x800, System Layer: QEMU Redis 7.0.4 Test: GET - Parallel Connections: 50 Redis 7.0.4 Test: SET - Parallel Connections: 50 Redis 7.0.4 Test: GET - Parallel Connections: 500 Redis 7.0.4 Test: LPOP - Parallel Connections: 50 Redis 7.0.4 Test: SADD - Parallel Connections: 50 Redis 7.0.4 Test: SET - Parallel Connections: 500 Redis 7.0.4 Test: GET - Parallel Connections: 1000 Redis 7.0.4 Test: LPOP - Parallel Connections: 500 Redis 7.0.4 Test: LPUSH - Parallel Connections: 50 Redis 7.0.4 Test: SADD - Parallel Connections: 500 Redis 7.0.4 Test: SET - Parallel Connections: 1000 Redis 7.0.4 Test: LPOP - Parallel Connections: 1000 Redis 7.0.4 Test: LPUSH - Parallel Connections: 500 Redis 7.0.4 Test: SADD - Parallel Connections: 1000 Redis 7.0.4 Test: LPUSH - Parallel Connections: 1000 BlogBench 1.1 Test: Read Final Score > Higher Is Better BlogBench 1.1 Test: Write Final Score > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Add - Connections: 256 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Get - Connections: 256 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Set - Connections: 256 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 1 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 4 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Append - Connections: 256 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Delete - Connections: 256 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 16 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 32 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 64 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Prepend - Connections: 256 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 128 Operations Per Second > Higher Is Better Memcached mcperf 1.6.9 Method: Replace - Connections: 256 Operations Per Second > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 20 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 50 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 100 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 20 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 50 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 500 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 20 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 50 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 20 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 50 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 100 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 1000 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 20 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 50 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 500 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 20 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 50 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 100 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 20 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 50 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 500 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 100 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 20 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 50 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 500 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 100 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 1000 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 500 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 100 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 20 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 50 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 500 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 100 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 1000 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 20 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 50 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 500 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 100 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 1000 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 20 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 50 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 500 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Open - Threads: 1000 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 100 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 1000 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 20 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 50 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 500 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 100 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 1000 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 500 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 100 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 1000 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 500 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 100 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 1000 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 500 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Create - Threads: 1000 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Delete - Threads: 1000 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: Rename - Threads: 1000 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 20 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 50 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 100 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 20 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 50 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 500 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 100 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 1000 - Files: 100000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 20 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 50 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 500 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 100 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 1000 - Files: 1000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 500 - Files: 10000000 Ops per sec > Higher Is Better Apache Hadoop 3.3.6 Operation: File Status - Threads: 1000 - Files: 10000000 Ops per sec > Higher Is Better ebizzy 0.3 Records/s > Higher Is Better PHPBench 0.8.1 PHP Benchmark Suite Score > Higher Is Better overnight with full access, 48gb memory . 348317 |============================= PostgreSQL 16 Scaling Factor: 1 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling: Buffer Test - Test: Normal Load - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling: Buffer Test - Test: Normal Load - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling: Buffer Test - Test: Heavy Contention - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling: Buffer Test - Test: Heavy Contention - Mode: Read Write TPS > Higher Is Better InfluxDB 1.8.2 Concurrent Streams: 4 - Batch Size: 10000 - Tags: 2,5000,1 - Points Per Series: 10000 val/sec > Higher Is Better InfluxDB 1.8.2 Concurrent Streams: 64 - Batch Size: 10000 - Tags: 2,5000,1 - Points Per Series: 10000 val/sec > Higher Is Better InfluxDB 1.8.2 Concurrent Streams: 1024 - Batch Size: 10000 - Tags: 2,5000,1 - Points Per Series: 10000 val/sec > Higher Is Better SQLite 3.30.1 Threads / Copies: 1 Seconds < Lower Is Better Perl Benchmarks Test: Pod2html Seconds < Lower Is Better Perl Benchmarks Test: Interpreter Seconds < Lower Is Better Apache CouchDB 3.3.2 Bulk Size: 100 - Inserts: 1000 - Rounds: 30 Seconds < Lower Is Better overnight with full access, 48gb memory . 6.004 |============================== Apache CouchDB 3.3.2 Bulk Size: 100 - Inserts: 3000 - Rounds: 30 Seconds < Lower Is Better overnight with full access, 48gb memory . 6.004 |============================== Apache CouchDB 3.3.2 Bulk Size: 300 - Inserts: 1000 - Rounds: 30 Seconds < Lower Is Better overnight with full access, 48gb memory . 6.004 |============================== Apache CouchDB 3.3.2 Bulk Size: 300 - Inserts: 3000 - Rounds: 30 Seconds < Lower Is Better overnight with full access, 48gb memory . 6.005 |============================== Apache CouchDB 3.3.2 Bulk Size: 500 - Inserts: 1000 - Rounds: 30 Seconds < Lower Is Better overnight with full access, 48gb memory . 6.004 |============================== Apache CouchDB 3.3.2 Bulk Size: 500 - Inserts: 3000 - Rounds: 30 Seconds < Lower Is Better overnight with full access, 48gb memory . 6.004 |============================== SQLite Speedtest 3.30 Seconds < Lower Is Better PHP Micro Benchmarks Test: Zend bench Seconds < Lower Is Better overnight with full access, 48gb memory . 1.033 |============================== PHP Micro Benchmarks Test: Zend micro_bench Seconds < Lower Is Better overnight with full access, 48gb memory . 3.576 |==============================