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
This writes over 55K transactions per second in its current form. Spring CRUD adds a database write for each index. So, am writing at 280k ops in the database. If I don't flush the database I also get read traffic which shows up as 375K ops in the database.
With Redis, this should be better. This is running on one GCP 16 core machine.
The text was updated successfully, but these errors were encountered:
Pipelining in the transaction write after changing the transaction key to a hash tag with the account number in it would probably cause a 2-3x throughput improvement
This writes over 55K transactions per second in its current form. Spring CRUD adds a database write for each index. So, am writing at 280k ops in the database. If I don't flush the database I also get read traffic which shows up as 375K ops in the database.
With Redis, this should be better. This is running on one GCP 16 core machine.
The text was updated successfully, but these errors were encountered: