The devil is always in the details with benchmarks. I suggest you make an example workload of what t
The devil is always in the details with benchmarks. I suggest you make an example workload of what these writes will be and try them in a D1 test database.
We have many times done millions of rows read per second and thousands of writes, but that's within a query. The problem with remote queries is the network between your worker and the database and everything in between. Once your query reaches the database, it's very very fast.
700 is not an unusually high number, we saw higher, but again, it depends on the specifics..
My suggestion is to make a test workload and try it out.
We have many times done millions of rows read per second and thousands of writes, but that's within a query. The problem with remote queries is the network between your worker and the database and everything in between. Once your query reaches the database, it's very very fast.
700 is not an unusually high number, we saw higher, but again, it depends on the specifics..
My suggestion is to make a test workload and try it out.
