Remove 2048 Remove Benchmarking Remove Virtualization
article thumbnail

Using Huge Pages with PostgreSQL Running Inside Kubernetes

Percona

Modern servers operate with terabytes of RAM, and by default, processors work with virtual memory address translation for each 4KB page. OS maintains a huge list of allocated and free pages to make slow but reliable address translation from virtual to physical. Huge pages make PostgreSQL faster; can we implement it in Kubernetes?

C++ 105
article thumbnail

How to analyze PostgreSQL benchmark performance with HammerDB

HammerDB

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

HammerDB v4.3 New Features Pt1: Graphical Metrics for PostgreSQL

HammerDB

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.

Metrics 63
article thumbnail

SQL Server I/O Basics Chapter #2

SQL Server According to Bob

​​ The following table outlines the virtual protection states. Page State Virtual Protection State Dirty Read Write ​​ during the modification. Page State Virtual Protection State Dirty Read Write ​​ during the modification.

Servers 40