Re: [I] ByteBuf returned by BookKeeper triggers CRC Checksum calculation when calling "readBytes" [bookkeeper]

Tue, 28 May 2024 23:53:15 -0700 


lhotari commented on issue #4372:
URL: https://github.com/apache/bookkeeper/issues/4372#issuecomment-2136668442

   > I also found the checksum cost a lot of CPU <img alt="image" width="1726" 
src="https://private-user-images.githubusercontent.com/5436568/334629475-85f3685e-070a-49a6-ae2b-d941e3b265ef.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTY5NjU2NzYsIm5iZiI6MTcxNjk2NTM3NiwicGF0aCI6Ii81NDM2NTY4LzMzNDYyOTQ3NS04NWYzNjg1ZS0wNzBhLTQ5YTYtYWUyYi1kOTQxZTNiMjY1ZWYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDUyOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA1MjlUMDY0OTM2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9N2M4MDMwZDVhMzRjZDY5Yjk0YzdhMDIxZDM4MzZmMWEzYjA5MGQ4MjFhYjMyMDBhMjA3MDZhNjNjYTljZmExNiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Y6bFbjJkicB8skWh_KdgdXb2NcrayCWbPcew2LtAbm4";>
   
   @hangc0276 I guess it is expected to consume a lot of CPU? In Enrico's case, 
the flamegraph doesn't seem to be valid and my assumption was that adding 
`-XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints` to JVM options would 
fix it since it's recommended to use these JVM options to get proper results 
while profiling.


-- 
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]

Reply via email to