Log caching of shards in the query
GoogleCodeExporter opened this issue · comments
Reported by W.Briggs...@gmail.com
Currently cache is only logged for the initial or base URL for the test. When
adding multiple shards to the query the cache information only pertains to the
base URL and ignores the cache stats of the shard cores.
I think individual monitoring as opposed to aggregated statistics will make the
most sense. That way you can pick individual shards in the GUI and compare
differences in hit rates, evictions, etc.
Original issue reported on code.google.com by tflo...@gmail.com on 18 Aug 2011 at 10:20