You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Liya Fan (Jira)" <ji...@apache.org> on 2022/01/07 02:08:00 UTC
[jira] [Commented] (ARROW-15259) [Java] [Benchmarking] Large stdout when running benchmarks
[ https://issues.apache.org/jira/browse/ARROW-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470293#comment-17470293 ]
Liya Fan commented on ARROW-15259:
----------------------------------
[~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?
> [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)