IOhacker commented on PR #5429: URL: https://github.com/apache/fineract/pull/5429#issuecomment-3828861690
1. Externalize (if the person requires to override) and add CPU aware 2. How we can check that this change has solved the problem that you have written in the PR description "The existing SimpleAsyncTaskExecutor creates a new thread for every event, leading to thread exhaustion under load (200+ concurrent users). This causes JVM memory exhaustion and service outages." The problem that you describe is present in Read, Write, Batch Instance mode? https://fineract-academy.com/fineract-instance-types/ https://fineract.apache.org/docs/current/ El sáb, 31 ene 2026 a las 11:13, Krishna ***@***.***>) escribió: > *DeathGun44* left a comment (apache/fineract#5429) > <https://github.com/apache/fineract/pull/5429#issuecomment-3828854909> > > @IOhacker <https://github.com/IOhacker> Thank you for the feedback! > > To clarify the scope: > > 1. For pool sizing - should I externalize to FineractProperties, or > add CPU-aware defaults? > 2. For tests - are we talking looking for configuration verification > tests, or load/stress tests? > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/fineract/pull/5429#issuecomment-3828854909>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ALD2ZAS5T4QADNNXJIRBFGD4JTPBXAVCNFSM6AAAAACTRGH2SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYHA2TIOJQHE> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- 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]
