GitHub user YongGoose added a comment to the discussion: Proposal for global_table Cleanup Optimization in Seata Transacion Coordinator
Given the conclusion in #6615, it seems best to proceed with a multi-threaded approach for now and evolve the solution gradually. I'll explore **ways to distribute the data** and tune the number of threads based on `queryLimit`, and conduct some analysis accordingly. > I’ve scheduled a session with a colleague who contributes actively to Apache > Beam for next Saturday—we plan to run some experiments and analyze the > results together. I’ll be sure to share our findings after that. In the meantime, if you have any thoughts or feedback on Option 1 (Enhance TC Internal Multi-threaded Cleanup), please feel free to share! GitHub link: https://github.com/apache/incubator-seata/discussions/7362#discussioncomment-13268998 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
