Remove Architecture Remove Benchmarking Remove Operating System Remove Tuning
article thumbnail

What Adrian Did Next?—?Part 2?—?Sun Microsystems

Adrian Cockcroft

Another big jump, but now it was my job to run benchmarks in the lab, and write white papers that explained the new products to the world, as they were launched. I was mostly coding in C, tuning FORTRAN, and when I needed to do a lot of data analysis of benchmark results used the S-PLUS statistics language, that is the predecessor to R.

Tuning 52
article thumbnail

The top 5 reasons to run your own database benchmarks

HammerDB

Some opinions claim that “Benchmarks are meaningless”, “benchmarks are irrelevant” or “benchmarks are nothing like your real applications” However for others “Benchmarks matter,” as they “account for the processing architecture and speed, memory, storage subsystems and the database engine.”

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Is It a Read Intensive or a Write Intensive Workload?

Percona

Let’s examine the TPC-C Benchmark from this point of view, or more specifically its implementation in Sysbench. The illustrations below are taken from Percona Monitoring and Management (PMM) while running this benchmark. Let’s now look at the operating system level. Analyzing read/write workload by counts.

article thumbnail

SQL Server I/O Basics Chapter #1

SQL Server According to Bob

Many of these systems support I/O ordering with a stable media cache and subsequently combine and/or split I/O requests across available subsystem resources to complete the storing to physical media. For specific information on I/O tuning and balancing, you will find more details in the following document.

Servers 40
article thumbnail

The evolution of single-core bandwidth in multicore processors

John McCalpin

This metric is interesting because we don’t always have the luxury of parallelizing every application we run, and our operating systems almost always process each call (e.g., GHz, 1530 GB/s peak BW from 6 HBM stacks), I see single-thread sustained memory bandwidth of 304 GB/s on the ReadOnly benchmark used here.

article thumbnail

Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform

High Scalability

Over time, costs for S3 and GCS became reasonable and with Egnyte’s storage plugin architecture, our customers can now bring in any storage backend of their choice. In general, Egnyte connect architecture shards and caches data at different levels based on: Amount of data. SOA architecture based on REST APIs. Edge caching.