custom_benchmarks 0.0.1 → 0.0.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. data/README +10 -0
  2. data/lib/custom_benchmarks.rb +3 -1
  3. metadata +2 -2
data/README CHANGED
@@ -86,3 +86,13 @@ Anonymous SVN access:
86
86
  $ svn checkout svn://rubyforge.org/var/svn/zventstools
87
87
 
88
88
  Author: Tyler Kovacs (tyler dot kovacs at gmail dot com)
89
+
90
+ == What's Next?
91
+ * Default integrations: It would be great if the plugin shipped with a
92
+ number of default integrations for logging things like acts_as_ferret
93
+ and acts_as_solr, memcached latency and call count and activerecord SQL
94
+ call count.
95
+ * Log File Analyzer: One we have all this great data written to the log,
96
+ how do we consume it? It makes sense to write an analyzer similar to
97
+ the production_log_analyzer, but one that can adapt to arbitrary data
98
+ written to the log (provided it fits a certain format).
@@ -69,10 +69,12 @@
69
69
  module ActionController #:nodoc:
70
70
  module CustomBenchmarking #:nodoc:
71
71
  def self.included(base)
72
+ base.extend(ClassMethods)
73
+
72
74
  base.class_eval do
75
+ alias_method :perform_action_without_custom_benchmark, :perform_action
73
76
  alias_method :perform_action, :perform_action_with_custom_benchmark
74
77
  end
75
- base.extend(ClassMethods)
76
78
  end
77
79
 
78
80
  module ClassMethods
metadata CHANGED
@@ -3,8 +3,8 @@ rubygems_version: 0.8.10
3
3
  specification_version: 1
4
4
  name: custom_benchmarks
5
5
  version: !ruby/object:Gem::Version
6
- version: 0.0.1
7
- date: 2006-10-31
6
+ version: 0.0.2
7
+ date: 2006-11-07
8
8
  summary: Easily allows custom information to be included in the benchmark log line at the end of each request.
9
9
  require_paths:
10
10
  - lib