# Velocità programma

**URL:** <https://www.ruby-forum.com/t/velocita-programma/243607>\
**Category:** IT\
**Created:** [December 9, 2015, 10:36pm UTC](https://www.ruby-forum.com/t/velocita-programma/243607 "2015-12-09T22:36:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sadaf\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/858c86/32.png) [@Sadaf\_N](https://www.ruby-forum.com/u/Sadaf_N)\
**Post date:** [December 9, 2015, 10:36pm UTC](https://www.ruby-forum.com/t/velocita-programma/243607/1 "2015-12-09T22:36:59Z")

</div>

Qual è il modo più intelligente per capire quanto sia efficiente il  
proprio programma?  
Come faccio a capire che potrebbe metterci molto meno tempo ad eseguire  
un’azione cambiando qualcosa?

---

<div class="post-metadata">

**Author:** ![codefun](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c0e974/32.png) [@codefun](https://www.ruby-forum.com/u/codefun)\
**Post date:** [December 10, 2015, 8:47am UTC](https://www.ruby-forum.com/t/velocita-programma/243607/2 "2015-12-10T08:47:06Z")

</div>

Usa un profiler [GitHub - ruby-prof/ruby-prof: A ruby profiler. See https://ruby-prof.github.io for more information.](https://github.com/ruby-prof/ruby-prof) e concentrati  
sulle parti dove l’applicazione passa più tempo o dove è troppo lenta e  
dà fastidio a chi la usa.

Se è Rails vedi  
[http://ccaloha.cc/blog/2015/07/14/howto-performance-test-in-rails-4/](http://ccaloha.cc/blog/2015/07/14/howto-performance-test-in-rails-4/)

Vedi anche [GitHub - tmm1/perftools.rb: gperftools for ruby code](https://github.com/tmm1/perftools.rb) e  
[GitHub - tmm1/stackprof: a sampling call-stack profiler for ruby 2.2+](https://github.com/tmm1/stackprof)