DD
DD
I find that the root logger's filter added by log4j2Metrics, reseted sometime after application started. Since my applcation have multiple context, it will trigger ApplicationEnvironmentPreparedEvent multiple times, and with `LoggingSystemShutdownListener`...
We saw many warning logs when things started, as shown below. (StuckThreadDetectionValve is inspired by tomcat)  so we think that the networking nio threads are all blocking and there...
While doing load testing, I found that metrics.record had blocking issues. Besides marking it as synchronized, can we make a lock-free implementation for it?
changes: 1.in `handleMatcherEventMargin`, split updatePositionForMarginTrade into 2 function, for calculate pnl in partial close 2.in `BALANCE_ADJUSTMENT` case, check the lockedMargin 3.add `checkAndLiquidateAllPositions`
### Your question 在使用分代 ZGC 时,发现 jraft 在高 QPS 场景下产生了大量 GC 跨代引用,导致 GC 扫描和吞吐量明显下降。 ### Your scenes 我们在disruptor的对象复用中,又new了新的对象,导致老对象持有新对象。 具体而言: 1. FSMCallerImpl中enqueueTask 2.ReadOnlyServiceImpl中new Bytes(reqCtx) 3.NodeImpl中new LogEntry() 4.LogManagerImpl中appendEntries ### Your advice 我们是否有可能把translator中new对象的行为去掉,也搞成复用对象。...