@gianm I saw lots of time eat up by r/w lock itself, I doubt r/w lock is the root cost of high cpu occupy. To my knowledge the read lock is not needed, we can only keep the lock for add() and sort(), even the lock for sort() is also not needed due to sort() should only be called when persist at which moment the add() is not going to be called. but for safety, we can keep the lock for sort().
[ Full content available at: https://github.com/apache/incubator-druid/issues/6322 ] This message was relayed via gitbox.apache.org for [email protected]
