HammerDB
SEPTEMBER 24, 2024
The key findings of the article were as follows: This server had a HammerDB benchmark running against it. But why are we running a COPY operation during a benchmark anyway? So this COPY statement is coming from the schema build phase and not the HammerDB benchmark workload at all. and start the build running.
Percona
DECEMBER 20, 2023
Unfortunately, the performance in benchmarks is almost the same as for 4KB pages. Please check out the Why Linux HugePages are Super Important for Database Servers: A Case with PostgreSQL blog post for more information. Setup I recommend starting with 2MB huge pages because it’s trivial to set up. It’s easy with anydbver and k3d.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
HammerDB
NOVEMBER 22, 2021
This enables the user to compare and contrast performance across different benchmark scenarios. shared_preload_libraries = 'pg_stat_statements,pgsentinel' track_activity_query_size=2048 pg_stat_statements.save=on pg_stat_statements.track=all pgsentinel_pgssh.enable = true pgsentinel_ash.pull_frequency = 1 pgsentinel_ash.max_entries = 1000000.
Percona
MARCH 20, 2023
MySQL router, after the 2048 connection, could not serve anything more. As you can see, and as I was expecting, the three Proxies were behaving more or less the same, serving the same number of operations (they were capped, so why not) until they weren’t. That allows it to go a bit further.
n0derunner
MARCH 13, 2020
Why do we tend to use 1MB IO sizes for throughput benchmarking? 8 Sectors = 4KB 128 Sectors = 64KB 1024 Sectors = 512KB 2048 Sectors = 1024KB (1MB). First things First. CDC 9762 SMD disk drive from 1974. Normally this is reported in “sectors” which are 512bytes in size. Using iostat.
SQL Server According to Bob
JANUARY 11, 2020
2000, and 2005 - replaced with SQLIOSim)
Expert insights. Personalized for you.
68 
Let's personalize your content