[
https://issues.apache.org/jira/browse/ARROW-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470326#comment-17470326
]
Elena Henderson commented on ARROW-15259:
-----------------------------------------
[~fan_li_ya] You should be able to reproduce it by running this command:
{code:java}
archery benchmark run 06fee4545535fc4a1af5c08b4e524ffb89bc7868 --language java
--output /tmp/tmpklnnnr1s --repetitions 1 --src arrow{code}
If you save all the logs generated by Java benchmarks command into a file (it
will be around 12GB) or watch memory usage using `top` while running java
benchmarks, you will see that Memory Usage goes up to 12GB.
Java benchmarks started to generate these large logs starting with ARROW-15058.
> [Java] [Benchmarking] Large stdout when running benchmarks
> ----------------------------------------------------------
>
> Key: ARROW-15259
> URL: https://issues.apache.org/jira/browse/ARROW-15259
> Project: Apache Arrow
> Issue Type: Bug
> Components: Benchmarking, Java
> Reporter: Elena Henderson
> Priority: Major
>
> Since ARROW-15058 running the Java benchmarks results in stdout logs that are
> extremely large (we're seeing them at ~14gb). This is disrupting running
> benchmarks on conbench.
> We've temporarily worked around this by disabling stdout logging entirely,
> but this will make debugging issues in the future much harder.
> Is there any way to reduce the volume of stdout logging when running these
> benchmarks?
> cc [~dsusanibara] [~fan_li_ya]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
