Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
I'm not sure this possible but chatting w/ J-D after he finished helping a crew who had a slow scan, we need ways to help folks figure out why stuff is slow on the server side. In this case, the user had a region that had gigs of deletes in it that had to be skipped before the scanner got to a value to return so scans looked slow though working 'correctly'. If the user could enable a DebugFilter than did counts of what Scans were skipping and size of data skipped among other things, it might help w/ the situation above – and perhaps with others (What else could we count in a filter?)