klT45 commented on issue #7839: URL: https://github.com/apache/shenyu/issues/7839#issuecomment-6309017749
Hi, I'd like to work on this. Plan, subject to your feedback: 1. Reproduce on the HTTP long-polling path: N independent per-rule commits in one namespace; record `ruleService` lookups, full serialization/MD5 counts per event and after convergence. 2. Add an opt-in, bounded coalescing layer at the cache/notification boundary (dirty group + generation counter + short window). Per-event business/audit callbacks, DELETE/UPDATE ordering and after-commit boundaries stay untouched; default behaviour is unchanged. 3. Handle writes that arrive during a rebuild (generation must not be cleared before it is consumed), namespace isolation and rollback. 4. Tests: concurrent independent events, update-then-delete ordering, rollback, coalescing-disabled fallback; keep #7181's import-batching tests intact. 5. Report before/after numbers following the #7650 benchmark contract, plus the added-notification-latency budget and overload behaviour. I'd like to land this as two PRs: mechanism + tests (default off) first, then measurements. First PR within a week. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
