Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Ozone read operation turned out to be slow mainly because we do a new UGI.getCurrentUser for block token for each of the calls.
We need to cache the block token / UGI.getCurrentUserCall() to make it faster.
To reproduce:
Checkout: https://github.com/elek/hadoop-ozone/tree/mocked-read
cd hadoop-ozone/client export MAVEN_OPTS=-agentpath:/home/elek/prog/async-profiler/build/libasyncProfiler.so=start,file=/tmp/profile-%t-%p.svg mvn compile exec:java -Dexec.mainClass=org.apache.hadoop.ozone.client.io.TestKeyOutputStreamUnit -Dexec.classpathScope=test
Attachments
Attachments
Issue Links
- links to