defensivedepth
06/04/2020, 1:05 PMZach Zeid
06/04/2020, 1:07 PMfritz
06/04/2020, 1:32 PM.timer ON
modeZach Zeid
06/04/2020, 1:33 PMzwass
Zach Zeid
06/04/2020, 5:27 PMzwass
Zach Zeid
06/04/2020, 5:31 PMtools
onto my test instancezwass
Zach Zeid
06/04/2020, 5:40 PMseph
Zach Zeid
06/04/2020, 5:49 PMseph
I think there’s also a fundamental issue where the profiler can only guess at likely cpu and memory consumption. Much depends on your fleet specifics. Things like the shard parameter, or create test groups of hosts is going to be a more real-world way to handle this.
Zach Zeid
06/04/2020, 5:54 PMshard
work if it's distributed among 100s of servers, each with a config of shard: 1
?zwass
Zach Zeid
06/04/2020, 5:55 PMosquery.conf
how do the servers know they're a part of that 1%?seph
The shard key works by hashing the hostname then taking the quotient 255 of the first byte. This allows us to select a deterministic ‘preview’ for the query, this helps when slow-rolling or testing new queries.
zwass
Zach Zeid
06/04/2020, 5:57 PM