From: normalperson@...
Date: 2014-01-19T10:41:22+00:00
Subject: [ruby-core:59869] [ruby-trunk - Bug #9430] [Open] [PATCH] benchmark/driver: avoid large alloc in driver process

Issue #9430 has been reported by Eric Wong.

----------------------------------------
Bug #9430: [PATCH] benchmark/driver: avoid large alloc in driver process
https://bugs.ruby-lang.org/issues/9430

* Author: Eric Wong
* Status: Open
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* Category: misc
* Target version: current: 2.2.0
* ruby -v: trunk
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
Using backtick to capture output on bm_so_reverse_complement leads
to unpredictable results because the Ruby process capturing needs to
slurp the 25M output of that benchmark, meaning the GC run of the
driver process ends up bottlenecking the processes being
benchmarked.

Instead, just redirect to File::NULL which is /dev/null on Unix-like
systems.

----------------------------------------------------------------
The following changes since commit 41bdefd56f628781a19f5d5d5f6a9a05cb4f3e9e:

  tracepoint.c: disable tracepoint (2014-01-19 08:56:58 +0000)

are available in the git repository at:

  git://80x24.org/ruby.git benchdriver-system

for you to fetch changes up to c4ac0560c88e45e026fdfaa313b6417458da53ce:

  benchmark/driver: avoid large alloc in driver process (2014-01-19 10:34:47 +0000)

----------------------------------------------------------------
Eric Wong (1):
      benchmark/driver: avoid large alloc in driver process

 benchmark/driver.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


---Files--------------------------------
0001-benchmark-driver-avoid-large-alloc-in-driver-process.patch (1002 Bytes)


-- 
http://bugs.ruby-lang.org/