c) I tried another cloud hosting provider (E2E Networks) and just the raw performance numbers (with default configuration) are blowing Hetzner out of the water.
I noticed that on E2E, the root filesystem is mounted with the following options:
/dev/xvda on / type ext4
(rw,noatime,nodiratime,nobarrier,errors=remount-ro,stripe=512,data="">
whereas on Hetzner, it is mounted with the following options:
/dev/nvme0n1p3 on / type ext4
(rw,relatime,data="">
How much of a difference can this have on absolute TPS numbers?
-- Saurabh.
- Follow-Ups:
- References:
- Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- From: Saurabh Nanda
- Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- From: Saurabh Nanda
- Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- From: Saurabh Nanda
- Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- From: Justin Pryzby
- Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- From: Saurabh Nanda
- Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- From: Saurabh Nanda
- Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- Prev by Date: Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- Next by Date: pg_locks - what is a virtualxid locktype
- Previous by thread: Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- Next by thread: Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
- Index(es):