MeihanLi opened a new issue, #11293: URL: https://github.com/apache/pinot/issues/11293
We recently observed that reloading segments, even reloading a small set of segments one by one for a partial upsert table (~90 segment replicas and each replica is around 650MB) can cause a significant increase in CPU usage (~30-40%). Server tenant: <img width="1480" alt="image" src="https://github.com/apache/pinot/assets/42751784/bdd139b6-7b2a-4be5-bfda-97a8129afe25";> We have looked into one server and even we only reloaded 11 segments during the time, the CPU usage is pretty high. Server (# of cores): <img width="677" alt="image" src="https://github.com/apache/pinot/assets/42751784/a8a16437-3172-4ffc-b038-0a20948d462a";> We are using default max.parallel.refresh.threads = 1 in HelixInstanceDataManagerConfig. It means there is no parallel during segment reloading. In other words, the server load mainly comes from refreshing a single segment. Is there a way to improve the performance? This is blocking our schema evolution for such upsert tables and any suggestions or ideas are appreciated. Thanks! -- 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: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
