11 ms·
If I’m reading this right, the insertion benchmark for TrailBase C# is hitting about 4.4k inserts of relatively small records per second per core. What’s the b
by twoodfin 2y ago
If I’m reading this right, the insertion benchmark for TrailBase C# is hitting about 4.4k inserts of relatively small records per second per core.
What’s the bottleneck at that point? That number seems small even when stacked up against much slower examples.
- deleted 2y ago[deleted]
- trailbase 2y agoThe C# insertion benchmark yields roughly 100000k inserts per 5.7s, so it's more like 17.5k inserts per second. A few observations: - Both benchmark driver and server are running locally on my laptop, completely saturating the machine. - I've managed to achieve higher throughput with rust. At least part of it is probably that the client side is lighter on my already saturated machine. - I've found that I'm getting roughly 3x the performance on a pretty humble 8700G desktop. - I've found the file-system to have a non-trivial impact. - The benchmark is only as fast as the bottleneck 50cm in front of the screen managed to make it run. The benchmark driver is here: https://github.com/trailbaseio/trailbase-benchmark/tree/main/benchmarks/trailbase_dotnet https://github.com/trailbaseio/trailbase-benchmark/tree/main.... Dotnet is super swift, so I'd be surprised if it couldn't be further optimized (whereas Dart and Node are fairly client-side bottlenecked).