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 Mar 27, 2021. It is now read-only.
I want to analyze how Heroic behaves when BigTable is under severe load. As I understand it, Heroic experiences this as very long response times or time-outs and that's it.
• is that last statement correct or is there another way that BigTable exposes degraded performance to clients (e.g. 5xx errors)?
• what tools (e.g. the BigTable emulator) are available to perform such analysis?
• do you have any tips for responding to degraded BigTable performance?
...
TL;DR: seemingly a couple of hot tablet servers utterly cripple the entire cluster's IO throughput. Cluster CPU also hits the floor, except for the 2 hot tablet servers.
The text was updated successfully, but these errors were encountered:
So whilst there were some suggestions from #bigtable, nothing usable was surfaced. Then after some time, Adam Steele ([email protected]) presented his fork of the BT emulator, which supports jittered delayed responses which suits our needs perfectly.
This has been trialled (code is currently in a patch file) and seems to work as advertised, which is great news.
From #bigtable:
The text was updated successfully, but these errors were encountered: