Joran Dirk Greef
@joran.tigerbeetle.com
Creator, Founder and CEO of @tigerbeetle.com — the financial transactions database designed for mission critical safety and performance.
Reposted by Joran Dirk Greef
Reposted by Joran Dirk Greef
Yes, it was really interesting to learn that TigerBeetle was inspired by research out of UW–Madison on storage faults.
I’ve also heard great things about their database group.
I’ve also heard great things about their database group.
August 1, 2025 at 3:45 PM
Yes, it was really interesting to learn that TigerBeetle was inspired by research out of UW–Madison on storage faults.
I’ve also heard great things about their database group.
I’ve also heard great things about their database group.
Haha! There was no side_letter.
July 6, 2025 at 6:05 PM
Haha! There was no side_letter.
Reposted by Joran Dirk Greef
Okay we're done with Benchmarking. Bringing up the whole Tigerbeetle team to take bows. Calling out the individual work each person did on the benchmarking demo and the conference.
June 20, 2025 at 3:23 PM
Okay we're done with Benchmarking. Bringing up the whole Tigerbeetle team to take bows. Calling out the individual work each person did on the benchmarking demo and the conference.
Reposted by Joran Dirk Greef
Picture of the vs screen, though I think it loses a bit without the animations and the music
(oh hey the lights turned yellow because the last race is with DuckDB)
They plan to release the program so you can make your own database races
(oh hey the lights turned yellow because the last race is with DuckDB)
They plan to release the program so you can make your own database races
June 20, 2025 at 3:15 PM
Picture of the vs screen, though I think it loses a bit without the animations and the music
(oh hey the lights turned yellow because the last race is with DuckDB)
They plan to release the program so you can make your own database races
(oh hey the lights turned yellow because the last race is with DuckDB)
They plan to release the program so you can make your own database races
Reposted by Joran Dirk Greef
June 20, 2025 at 3:11 PM
Reposted by Joran Dirk Greef
Tigerbeetle also had the ability to do full replication and durability checks, since it was fast enough to afford to spend cycles on that.
That was at 10% contention. Now benchmarking 50% contention with the proprietary postgres million-dollar cluster. Gets 2 minute headstart vs tigerbeetle
That was at 10% contention. Now benchmarking 50% contention with the proprietary postgres million-dollar cluster. Gets 2 minute headstart vs tigerbeetle
June 20, 2025 at 3:08 PM
Tigerbeetle also had the ability to do full replication and durability checks, since it was fast enough to afford to spend cycles on that.
That was at 10% contention. Now benchmarking 50% contention with the proprietary postgres million-dollar cluster. Gets 2 minute headstart vs tigerbeetle
That was at 10% contention. Now benchmarking 50% contention with the proprietary postgres million-dollar cluster. Gets 2 minute headstart vs tigerbeetle
Reposted by Joran Dirk Greef
I mean they had the potential to change color, they just didn't until the closing keynote.
To the beat of the synthwave.
That is playing.
What a conference, man
Aaaaaanyway that was a benchmark visualization. Postgres avged 1k tps, tigerbeetle avged 300k tps for same latency levels
To the beat of the synthwave.
That is playing.
What a conference, man
Aaaaaanyway that was a benchmark visualization. Postgres avged 1k tps, tigerbeetle avged 300k tps for same latency levels
June 20, 2025 at 3:05 PM
I mean they had the potential to change color, they just didn't until the closing keynote.
To the beat of the synthwave.
That is playing.
What a conference, man
Aaaaaanyway that was a benchmark visualization. Postgres avged 1k tps, tigerbeetle avged 300k tps for same latency levels
To the beat of the synthwave.
That is playing.
What a conference, man
Aaaaaanyway that was a benchmark visualization. Postgres avged 1k tps, tigerbeetle avged 300k tps for same latency levels
Reposted by Joran Dirk Greef
June 20, 2025 at 3:04 PM
Reposted by Joran Dirk Greef
THE SYNTHWAVE HAS STARTED
June 20, 2025 at 3:02 PM
THE SYNTHWAVE HAS STARTED
Reposted by Joran Dirk Greef
client runs on separate machine. Proprietary cluster users anonymized. Missed a bit of theother benchmark details.
"The time has come to race."
Gonna replay the real performance traces for us. Showing that now for psql, plus analytic database
"The time has come to race."
Gonna replay the real performance traces for us. Showing that now for psql, plus analytic database
June 20, 2025 at 3:02 PM
client runs on separate machine. Proprietary cluster users anonymized. Missed a bit of theother benchmark details.
"The time has come to race."
Gonna replay the real performance traces for us. Showing that now for psql, plus analytic database
"The time has come to race."
Gonna replay the real performance traces for us. Showing that now for psql, plus analytic database
Reposted by Joran Dirk Greef
Again, this ONLY does OLTP. No general-purpose processing, no custom data, no user passwords or workflow state machines, just accounts and debits/credits, nothing else. Specialization gives special interfaces gives power.
Benchmark time! Every db [except cluster?] runs on i8g.16xlarge...
Benchmark time! Every db [except cluster?] runs on i8g.16xlarge...
June 20, 2025 at 3:02 PM
Again, this ONLY does OLTP. No general-purpose processing, no custom data, no user passwords or workflow state machines, just accounts and debits/credits, nothing else. Specialization gives special interfaces gives power.
Benchmark time! Every db [except cluster?] runs on i8g.16xlarge...
Benchmark time! Every db [except cluster?] runs on i8g.16xlarge...