2 x Intel Xeon E5-2697 v3 testing with a Dell PowerEdge R630 [0CNCJW] (2.12.1 BIOS) and Microsoft Basic Display on Microsoft Windows Server 2012 R2 Standard Build 9600 via the Phoronix Test Suite.
Processor: 2 x Intel Xeon E5-2697 v3 @ 2.60GHz (28 Cores / 56 Threads), Motherboard: Dell PowerEdge R630 [0CNCJW] (2.12.1 BIOS), Memory: 4 x 16384 MB M393A2G40DB0-CPB, Disk: 465GB DELL PERC H730P Mini Disk, Graphics: Microsoft Basic Display, Monitor: BQ GW765
OS: Microsoft Windows Server 2012 R2 Standard Build 9600, Kernel: 6.3.9600 (x86_64), Display Driver: 6.3.9600.16384, Compiler: GCC 8.3.0, File-System: NTFS, Screen Resolution: 1024x768
Processor Notes: CPU Microcode: 0000000043000000
Security Notes: __user pointer sanitization: Disabled
This is a benchmark of PostgreSQL using pgbench for facilitating the database benchmarks. Learn more via the OpenBenchmarking.org test page.
Scaling Factor: 10000 - Clients: 50 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 10000 - Clients: 100 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 10000 - Clients: 250 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 10000 - Clients: 50 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 10000 - Clients: 500 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 25000 - Clients: 1 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 25000 - Clients: 50 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 25000 - Clients: 100 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 25000 - Clients: 1 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 100 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 250 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 500 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 100 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 50 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 500 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 250 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1000 - Clients: 50 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
This is a simple benchmark of SQLite. At present this test profile just measures the time to perform a pre-defined number of insertions on an indexed database. Learn more via the OpenBenchmarking.org test page.
This is a benchmark of PostgreSQL using pgbench for facilitating the database benchmarks. Learn more via the OpenBenchmarking.org test page.
BlogBench is designed to replicate the load of a real-world busy file server by stressing the file-system with multiple threads of random reads, writes, and rewrites. The behavior is mimicked of that of a blog by creating blogs with content and pictures, modifying blog posts, adding comments to these blogs, and then reading the content of the blogs. All of these blogs generated are created locally with fake content and pictures. Learn more via the OpenBenchmarking.org test page.
This is a benchmark of PostgreSQL using pgbench for facilitating the database benchmarks. Learn more via the OpenBenchmarking.org test page.
This is a test of ebizzy, a program to generate workloads resembling web server workloads. Learn more via the OpenBenchmarking.org test page.
This is a benchmark of PostgreSQL using pgbench for facilitating the database benchmarks. Learn more via the OpenBenchmarking.org test page.
Scaling Factor: 100 - Clients: 100 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 250 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 500 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 100 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 500 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 250 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 50 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 100 - Clients: 50 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Perl benchmark suite that can be used to compare the relative speed of different versions of perl. Learn more via the OpenBenchmarking.org test page.
This is a benchmark of PostgreSQL using pgbench for facilitating the database benchmarks. Learn more via the OpenBenchmarking.org test page.
Scaling Factor: 25000 - Clients: 50 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E:
dropdb: error: connection to server at "localhost" (::1), port 7777 failed: Connection refused (0x0000274D/10061)
Scaling Factor: 1 - Clients: 500 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 500 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 250 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 100 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 100 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 250 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 50 - Mode: Read Only
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
Scaling Factor: 1 - Clients: 50 - Mode: Read Write
test2: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result.
BlogBench is designed to replicate the load of a real-world busy file server by stressing the file-system with multiple threads of random reads, writes, and rewrites. The behavior is mimicked of that of a blog by creating blogs with content and pictures, modifying blog posts, adding comments to these blogs, and then reading the content of the blogs. All of these blogs generated are created locally with fake content and pictures. Learn more via the OpenBenchmarking.org test page.
Processor: 2 x Intel Xeon E5-2697 v3 @ 2.60GHz (28 Cores / 56 Threads), Motherboard: Dell PowerEdge R630 [0CNCJW] (2.12.1 BIOS), Memory: 4 x 16384 MB M393A2G40DB0-CPB, Disk: 465GB DELL PERC H730P Mini Disk, Graphics: Microsoft Basic Display, Monitor: BQ GW765
OS: Microsoft Windows Server 2012 R2 Standard Build 9600, Kernel: 6.3.9600 (x86_64), Display Driver: 6.3.9600.16384, Compiler: GCC 8.3.0, File-System: NTFS, Screen Resolution: 1024x768
Processor Notes: CPU Microcode: 0000000043000000
Security Notes: __user pointer sanitization: Disabled
Testing initiated at 26 August 2022 17:05 by user Administrator.