You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.
Figure out how to run database-only tests on benchmark harness #29@sebastienros will look at ways to execute database-only (e.g. no web) tests in our benchmark harness. This will improve our ability to compare and analyze the performance of the database access stack or networking stack in a reproducible way without "noise" from the web implementation.
Sockets benchmarks #30 Raw sockets benchmark: @roji is now writing some benchmarks that don't actually use a database as a means to rule out low-level bottlenecks as the root cause for the differences we are seeing with .NET vs. JDBC, Linux vs. Windows and sync vs. async in Npgsql tests. We wonder if other teams have done this already, but it seems to have enough value to just do it again. If we are able to confirm the presence of low-level bottlenecks we can pass this test to someone else to do the profiling and analysis.
The text was updated successfully, but these errors were encountered:
Attendees: @ajcvickers @anpete @DamianEdwards @davidfowl @divega @roji @sebastienros
Current areas of investigation:
The text was updated successfully, but these errors were encountered: