Open asfimport opened 2 years ago
Liya Fan / @liyafan82: [~elena@ursacomputing.com] Sorry, I do not understand how the large stdout logs are generated. By running the benchmarks locally, I do not see so much logs. So how can I reproduce the problem locally?
BTW, what is the relation with ARROW-15058?
Elena Henderson / @ElenaHenderson: [~fan_li_ya] You should be able to reproduce it by running this command:
archery benchmark run 06fee4545535fc4a1af5c08b4e524ffb89bc7868 --language java --output /tmp/tmpklnnnr1s --repetitions 1 --src arrow
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.
Liya Fan / @liyafan82: Sorry [~elena@ursacomputing.com] I am having some problems running the command you provided:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) on project arrow-format: Compilation failure -> [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) on project arrow-plasma: Compilation failure -> [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) on project arrow-memory-core: Compilation failure -> [Help 1]
However, when I built the project manually, it worked fine.
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 @davisusanibar [~fan_li_ya]
Reporter: Elena Henderson / @ElenaHenderson
Note: This issue was originally created as ARROW-15259. Please see the migration documentation for further details.