[GitHub] [geode-benchmarks] nabarunnag opened pull request #56: GEODE-6444: Store GC logs in files

["nabarunnag (GitHub)" <gi...@apache.org>]

	* Store the GC logs in a file.
	* Print the GC logs in the System.out / System.err in parallel while the benchmark is being executed in parallel.
	* Using a thread pool for execution of runAsync and not depend on fork join pools

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/56 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] nabarunnag closed pull request #56: GEODE-6444: Store GC logs in files

["nabarunnag (GitHub)" <gi...@apache.org>]

[ pull request closed by nabarunnag ]

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/56 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] pivotal-jbarrett commented on issue #56: GEODE-6444: Store GC logs in files

["pivotal-jbarrett (GitHub)" <gi...@apache.org>]

@nabarunnag your comment says:
>Print the GC logs in the System.out / System.err in parallel while the benchmark is being executed in parallel.

The params are writing the GC logs to disk, so what is printing them to the console and why?


[ Full content available at: https://github.com/apache/geode-benchmarks/pull/56 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org

[GitHub] [geode-benchmarks] nabarunnag commented on issue #56: GEODE-6444: Store GC logs in files

["nabarunnag (GitHub)" <gi...@apache.org>]

Its not the just gc logs but everything  that the java process is spitting out when it is started using the shell, errors etc. Thats why we were contemplating nohup operation.

[ Full content available at: https://github.com/apache/geode-benchmarks/pull/56 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org