blocks|key|886093|text|要真正深入到您的代码中，请尝试stackprof。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|886094|这里有一个关于如何使用它的快速解决方案:安装gem：gem+install+stackprof。在你的代码中添加：require+'stackprof'并用下面的代码括起你想要检查的部分：|style|CODE|886095|StackProf.run(mode:+:cpu,+out:+'stackprof-output.dump')+do+++{YOUR_CODE}+end|886096|运行ruby脚本后，使用stackprof+stackprof.dump在终端中检查输出|886097|Mode:+cpu(1000)
Samples:+9145+(1.25%25+miss+rate)
GC:+448+(4.90%25)

+TOTAL++++(pct)+++++SAMPLES++++(pct)+++++FRAME
+++236+++(2.6%25)+++++++++231+++(2.5%25)+++++String#blank?
+++546+++(6.0%25)+++++++++216+++(2.4%25)+++++ActiveRecord::ConnectionAdapters::Mysql2Adapter#select
+++212+++(2.3%25)+++++++++199+++(2.2%25)+++++Mysql2::Client#query_with_timing
+++190+++(2.1%25)+++++++++155+++(1.7%25)+++++ERB::Util#html_escape``|code-block|syntax|javascript|886098|在这里，您可以看到所有需要花费大量时间的方法。现在最棒的部分是:要深入研究，只需执行stackprof+stackprof.dump+--method+String#blank?，您就可以获得特定方法的输出：|886099|String#blank?+(lib/active_support/core_ext/object/blank.rb:80)
++samples:+++231+self+(2.5%25)++/++++236+total+(2.6%25)
++callers:
++++112++(+++47.5%25)++Object#present?
++code:
++++++++++++++++++++++++++++++++++%7C++++80++%7C+++def+blank?
++187++++(2.0%25)+/+++187+++(2.0%25)++%7C++++81++%7C+++++self+!~+/[%5E[:space:]]/
++++++++++++++++++++++++++++++++++%7C++++82++%7C+++end|886100|而且您可以很容易地找出代码的哪一部分需要花费大量时间来运行。|886101|如果你想得到一个可视化的输出，使用stackprof+stackprof.dump+--graphviz+>>+stackprof.dot+(brew+install+graphviz)+dot+-T+pdf+-o+stackprof.pdf+stackprof.dot得到一个漂亮的PDF输出，它突出显示了需要很长时间才能运行的方法。|886102|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/tmm1/stackprof^0|F|9|0|0|Q|L|1L|J|0|0|24|0|C|O|0|0|16|1B|0|0|0|H|1G|1Z|L|2M|15|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@$A|1B|B|1C|F|G]|$A|1D|B|1E|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1F|8|@$A|1G|B|1H|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1I|8|@$A|1J|B|1K|F|G]]|9|@]|C|$]]|$1|L|3|M|5|N|7|1L|8|@]|9|@]|C|$O|P]]|$1|Q|3|R|5|6|7|1M|8|@$A|1N|B|1O|F|G]]|9|@]|C|$]]|$1|S|3|T|5|N|7|1P|8|@]|9|@]|C|$O|P]]|$1|U|3|V|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1R|8|@$A|1S|B|1T|F|G]|$A|1U|B|1V|F|G]|$A|1W|B|1X|F|G]]|9|@]|C|$]]|$1|Y|3|-4|5|6|7|1Y|8|@]|9|@]|C|$]]]|Z|$10|$5|11|12|13|C|$14|15]]]]

To really drill into your code try out <a href="https://github.com/tmm1/stackprof" rel="nofollow noreferrer">stackprof</a>.

Here's a quick solution on how to use it:
Install the gem: <code>gem install stackprof</code>. In your code add: <code>require 'stackprof'</code> and surround the part that you want to check with this:

<code>StackProf.run(mode: :cpu, out: 'stackprof-output.dump') do
 {YOUR_CODE}
end
</code>

After running your ruby script go check the output in the terminal with <code>stackprof stackprof.dump</code>:

<pre><code>Mode: cpu(1000)
Samples: 9145 (1.25% miss rate)
GC: 448 (4.90%)

 TOTAL (pct) SAMPLES (pct) FRAME
 236 (2.6%) 231 (2.5%) String#blank?
 546 (6.0%) 216 (2.4%) ActiveRecord::ConnectionAdapters::Mysql2Adapter#select
 212 (2.3%) 199 (2.2%) Mysql2::Client#query_with_timing
 190 (2.1%) 155 (1.7%) ERB::Util#html_escape``
</code></pre>

Here you can see all your methods that require a lot of time. Now the awesome part: To drill in just do <code>stackprof stackprof.dump --method String#blank?</code> and you get the output for the specific method:

<pre><code>String#blank? (lib/active_support/core_ext/object/blank.rb:80)
 samples: 231 self (2.5%) / 236 total (2.6%)
 callers:
 112 ( 47.5%) Object#present?
 code:
 | 80 | def blank?
 187 (2.0%) / 187 (2.0%) | 81 | self !~ /[^[:space:]]/
 | 82 | end
</code></pre>

And you can quite easily figure out which part of your code takes a lot of time to run.

If you want to get a visual output do <code>stackprof stackprof.dump --graphviz &gt;&gt; stackprof.dot</code> and using graphviz (<code>brew install graphviz</code>) <code>dot -T pdf -o stackprof.pdf stackprof.dot</code> get a beautiful PDF output, which highlights the methods that take a long time to run.

blocks|key|1100955|text|还有来自Ruby源代码中的ruby+-rprofile或等效的require+'profile'|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1100956|文档：|1100957|https://ruby-doc.org/stdlib-2.1.0/libdoc/profiler/rdoc/Profiler__.html|1100958|entityMap|0|LINK|mutability|MUTABLE|url^0|D|E|V|H|0|0|0|1Y|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|J|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|I]]]]

There is also <code>ruby -rprofile</code> or equivalently from within Ruby source, <code>require 'profile'</code>

Documentation:

<a href="https://ruby-doc.org/stdlib-2.1.0/libdoc/profiler/rdoc/Profiler__.html" rel="nofollow noreferrer">https://ruby-doc.org/stdlib-2.1.0/libdoc/profiler/rdoc/Profiler__.html</a>

Besides ruby-prof and and the core Benchmark class, what do you use to profile your Ruby code? In particular, how do you find the bottlenecks in your code? It almost feels like I need to work on my own little tool just to figure out where all the time is being spent in my code.

I realize ruby-prof provides this, but the output is frankly very confusing and doesn't make it easy to find out which actual blocks of your own code are the source of the issue (it tells you about which method calls took the most time though). So I'm not really getting as much out of it as I'd like, and haven't really been able to make use of it.

Perhaps I'm doing it wrong? Are there alternatives? Google searches don't bring up anything for me.

Profiling Ruby Code

除了ruby-prof和核心基准测试类，你还用什么来分析你的Ruby代码呢？特别是，您如何找到代码中的瓶颈？我几乎感觉我需要在我自己的小工具上工作，只是为了弄清楚我的代码中所有的时间都花在了哪里。我知道ruby-prof提供了这一点，但坦率地说，输出非常令人困惑，并且不容易找出您自己的代码的哪些实际块是问题的根源(它会...

问分析Ruby代码
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问分析Ruby代码EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问分析Ruby代码
EN