#684 FYI.

I merged this PR optimistically, but upon reflection I think I'm going to have to revert it.

1. I'd like to keep the recent items clearing functionality separate from the rest
2. I'd like to keep the buffer capacity tweaks separate from the rest
3. we can't change the public API as there are too many tools using this library for reading binlogs and we can't require all of them to update just for a progress bar
4. our regular users don't need the buffer utilization progress bar nor do they need the Log Processing Statistics
5. I haven't seen a wall clock time improvement for binlog loading, compared with the previous version. So not sure increasing the buffer is observably helping (at least in the windows case)

• I will spin up another PR for the Recent Clear function.
• I haven't found an improvement with buff capacity either, but that could be a Windows or hardware difference. Is there a way to add a "developer" mode flag?

Don't worry about it, I just pushed the revert:

efb0a57

I would like to avoid regular users paying any perf costs just for developer monitoring tooling.

Your buffer utilization progress bar is good, as well as the perf counters, but stuff like this is good to keep in the branch perhaps. Feel free to make a branch with the revert of efb0a57 and use it for local testing.

Don't think we need this in the main branch.