There are summaries that summarize too many ops, indicating we are not summarizing often enough

[NicholasCouri]

Fix #9908
Initial attempt to adjust the Summary Configuration options now that we do not rely on the Service to provide them:
a) MaxOps (from 1000 - 100 ops)
b) MaxAckWaitTime (from 10 mins down to 2 mins).

@vladsud - I'm not sure if changing idleTime right now, together with MaxOps is the right thing to do - should we wait for more data ? Currently, idleTime is 15 secs.

@agarwal-navin FYI.

[vladsud]

We need to put note into breaking.md and tell the world that

• we are changing settings (and say what is changed and how it will impact summarization)
• Ask each scenario to re-evaluate what is required for that scenario, and if our defaults are not good, provide their own (and describe a way to do so).

This is important, as most likely these settings will not work well for WB - their summaries are pretty heavy.
We should reach out to WB and Skyler's team to heads up.

Please also consider if we want to do #9990 first. I was looking around and discovered a lot of duplication there that sort made sense when we had it provided by service, but now it's one thing. I'd probably keep ISummaryConfiguration and move all summary related settings into ISummaryConfiguration.

[vladsud]

b) MaxAckWaitTime (from 10 mins down to 2 mins).

I'd rather open an issue to look into it. I see 1200 SummaryAckWaitTimeout events in telemetry over last 30 days. These are bugs. It's very hard to say without looking deeper into it if these bugs would be mitigated by lower timeout.
Please note this is not super-urgent (based on counts), but worth having an issue not to forget about it.

[vladsud]

I'm not sure if changing idleTime right now, together with MaxOps is the right thing to do - should we wait for more data ? Currently, idleTime is 15 secs.

I've opened #10008 with my thoughts on this.
Short story - I think idleTime knob should go away, and it should be calculated property based on unsummarized ops and maxOps, where maxIdle reaches zero when we have maxOps unsummarized ops, and reaches high numbers if we have few unsummarized ops.

[vladsud]

Looks good, but we have to put a warning in breaking.md about this change and the fact that each experience should test if it works for them and see if they need to provide their own settings as opposed to relying on defaults.