blocks|key|3473235|text|字符串连接的答案如下：https://web.archive.org/web/20090122123342/http://blog.cbciweb.com/2008/06/10/ruby-performance-use-double-quotes-vs-single-quotes|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3473236|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20090122123342/http://blog.cbciweb.com/2008/06/10/ruby-performance-use-double-quotes-vs-single-quotes^0|B|3L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The answer to the string concatenation is here: <a href="https://web.archive.org/web/20090122123342/http://blog.cbciweb.com/2008/06/10/ruby-performance-use-double-quotes-vs-single-quotes" rel="nofollow noreferrer">https://web.archive.org/web/20090122123342/http://blog.cbciweb.com/2008/06/10/ruby-performance-use-double-quotes-vs-single-quotes</a>

blocks|key|256356|text|嗯，有一些众所周知的做法，比如字符串连接比"#{value}“慢得多，但为了找出你的脚本在哪里消耗了大部分时间或超过了所需的时间，你需要进行分析。有一种叫ruby-prof的宝石。分析器可以引起您的注意，甚至是那些很少发生的性能问题。我一直在使用它，并且发现它非常有用。下面是直接从它的official+site获取的一些信息|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|256357|Ruby+prof是一个用于|256358|的快速代码分析器。它的功能包括：|blockquote|256359|256360|Ruby+-它是一个C扩展，因此比标准的分析器快很多倍。|style|BOLD|256361|Ruby+Modes-Ruby+prof可以测量许多不同的参数，包括调用时间、内存使用和对象分配。|256362|+reports++-可以生成文本和交叉引用的html报告|256363|Ruby+-类似于标准剖析器生成的报告|256364|图形配置文件-类似于GProf，它们显示一个方法运行多长时间，哪些方法调用它，以及它调用哪些方法。|256365|调用树配置文件-以适合KCacheGrind评测工具的调用树格式输出结果。|256366|+threads++-支持同时分析多个线程|256367|递归调用-支持分析递归方法调用|256368|entityMap|0|LINK|mutability|MUTABLE|url|http://ruby-prof.rubyforge.org/^0|3Z|D|0|0|0|0|0|K|8|0|0|A|0|0|9|0|B|8|0|0|1D|0|0|11|0|0|L|0|0|F|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@$A|1A|B|1B|1|1C]]|C|$]]|$1|D|3|E|5|6|7|1D|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1E|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1G|8|@$A|1H|B|1I|L|M]]|9|@]|C|$]]|$1|N|3|O|5|6|7|1J|8|@$A|1K|B|1L|L|M]]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1M|8|@$A|1N|B|1O|L|M]]|9|@]|C|$]]|$1|R|3|S|5|6|7|1P|8|@$A|1Q|B|1R|L|M]]|9|@]|C|$]]|$1|T|3|U|5|6|7|1S|8|@$A|1T|B|1U|L|M]]|9|@]|C|$]]|$1|V|3|W|5|6|7|1V|8|@$A|1W|B|1X|L|M]]|9|@]|C|$]]|$1|X|3|Y|5|6|7|1Y|8|@$A|1Z|B|20|L|M]]|9|@]|C|$]]|$1|Z|3|10|5|6|7|21|8|@$A|22|B|23|L|M]]|9|@]|C|$]]|$1|11|3|-4|5|6|7|24|8|@]|9|@]|C|$]]]|12|$13|$5|14|15|16|C|$17|18]]]]

Well, there are certain well known practices like string concatenation is way slower than "#{value}" but in order to find out where you script is consuming most of its time or more time than required, you need to do profiling. There is a ruby gem called ruby-prof. The profiler can bring to your notice even those performance issues that may rarely occur. I have been using it a lot and find it very helpful. Here is some information about it directly from its <a href="http://ruby-prof.rubyforge.org/" rel="noreferrer">official site</a>

<blockquote>
 ruby-prof is a fast code profiler for
 Ruby. Its features include:
 
 Speed - it is a C extension and therefore many times faster than the
 standard Ruby profiler.
 
 Modes - Ruby prof can measure a number of different parameters,
 including
 call times, memory usage and object allocations.
 
 Reports - can generate text and cross-referenced html reports
 
 Flat Profiles - similar to the reports generated by the standard Ruby
 profiler
 
 Graph profiles - similar to GProf, these show how long a method runs,
 which methods call it and which
 methods it calls.
 
 Call tree profiles - outputs results in the calltree format
 suitable for the KCacheGrind profiling
 tool.
 
 Threads - supports profiling multiple threads simultaneously
 
 Recursive calls - supports profiling recursive method calls
</blockquote>

blocks|key|4320583|text|您可以使用标准Benchmark+module测试各个代码段的性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4320584|你也可以在Ruby的不同实现(如1.9，Rubinius)上测试你的代码，看看这样做是否会加快速度。|4320585|当然，如果你的问题本质上是算法问题，那么就没有太多的理由担心像字符串连接速度这样的事情……|4320586|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ruby-doc.org/stdlib/libdoc/benchmark/rdoc/classes/Benchmark.html^0|7|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

You can test the performance of individual sections of code with the standard <a href="http://www.ruby-doc.org/stdlib/libdoc/benchmark/rdoc/classes/Benchmark.html" rel="nofollow noreferrer">Benchmark module</a>.

You could also test your code on different implementations of Ruby (eg 1.9, Rubinius) and see if that speeds things up.

Of course if your problems are algorithmic in nature then there's not too much point in worrying about things like string concatenation speeds...

blocks|key|4320610|text|您还可以在dTraceToolkit中使用一组用于Ruby的dTrace工具|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4320611|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There is also a set of dTrace tools for Ruby you can use in the dTraceToolkit

blocks|key|4320631|text|除了上面写的内容，我还推荐看一下Scaling+Ruby的截屏视频。它有一些关于如何编写更快的Ruby代码的有趣的技巧和技巧。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4320632|entityMap|0|LINK|mutability|MUTABLE|url|http://envycasts.com/products/scaling-ruby^0|G|C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Besides what's written above I also recommend watching the <a href="http://envycasts.com/products/scaling-ruby" rel="nofollow noreferrer">Scaling Ruby</a> screencast. It has some interesting tips&amp;tricks on how to write faster Ruby code.

I have written a Ruby application which parses lots of data from sources in different formats html, xml and csv files. How can I find out what areas of the code are taking the longest? 

Is there any good resources on how to improve the performance of Ruby applications? Or do you have any performance coding standards you always follow? 

For example do you always join your string with 

<pre><code>output = String.new
output &lt;&lt; part_one
output &lt;&lt; part_two
output &lt;&lt; '\n'
</code></pre>

or would you use

<pre><code>output = "#{part_one}#{part_two}\n"
</code></pre>

How can I find the performance bottlenecks in my Ruby application?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我写了一个Ruby应用程序，它可以解析来自不同格式的html、xml和csv文件的大量数据。我如何才能找出代码中哪些部分花费的时间最长？关于如何提高Ruby应用程序的性能，有没有什么好的参考资料？或者，你有没有任何你一直遵循的性能编码标准？例如，您是否总是将字符串与output = String.newoutput <...

问如何找到Ruby应用程序中的性能瓶颈？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何找到Ruby应用程序中的性能瓶颈？EN