From 677ce63d92b7725b0a11facddc1ba95f50f865df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gon=C3=A7alo=20Silva?= Date: Sun, 3 Apr 2011 01:09:34 +0100 Subject: profiling enabled under JRuby. Added documentation for workaround described in JRUBY-5650. --- railties/guides/source/performance_testing.textile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'railties') diff --git a/railties/guides/source/performance_testing.textile b/railties/guides/source/performance_testing.textile index ca11fbeec6..a515226b9a 100644 --- a/railties/guides/source/performance_testing.textile +++ b/railties/guides/source/performance_testing.textile @@ -223,7 +223,7 @@ h6. Profiling |_.Rubinius | yes | no | no | no | no | no | no | no | |_.JRuby | yes | no | no | no | no | no | no | no | -WARNING: Profiling under JRuby is currently unavailable because of a bug with rake and JRuby's +--profile.api+ option. You should resort exclusively to benchmarking. +NOTE: To profile under JRuby you'll need to run +export JRUBY_OPTS="-Xlaunch.inproc=false --profile.api"+ *before* the performance tests. h4. Understanding the Output @@ -309,8 +309,6 @@ h6. Output Availability |_.Rubinius | yes | yes | no | |_.JRuby | yes | yes | no | -WARNING: Again, profiling under JRuby is currently unavailable because of a bug with rake and JRuby's +--profile.api+ option. - h4. Tuning Test Runs Test runs can be tuned by setting the +profile_options+ class variable on your test class. -- cgit v1.2.3