BigW Consortium Gitlab
The use of ActiveSupport would slow down instrumented method calls by about 180x due to: 1. ActiveSupport itself not being the fastest thing on the planet 2. caller_locations() having quite some overhead The use of caller_locations() has been removed because it's not _that_ useful since we already know the full namespace of receivers and the names of the called methods. The use of ActiveSupport has been replaced with some custom code that's generated using eval() (which can be quite a bit faster than using define_method). This new setup results in instrumented methods only being about 35-40x slower (compared to non instrumented methods).
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
environments | Loading commit data... | |
initializers | Loading commit data... | |
locales | Loading commit data... | |
application.rb | Loading commit data... | |
aws.yml.example | Loading commit data... | |
boot.rb | Loading commit data... | |
database.yml.mysql | Loading commit data... | |
database.yml.postgresql | Loading commit data... | |
environment.rb | Loading commit data... | |
gitlab.teatro.yml | Loading commit data... | |
gitlab.yml.example | Loading commit data... | |
mail_room.yml | Loading commit data... | |
newrelic.yml | Loading commit data... | |
resque.yml.example | Loading commit data... | |
routes.rb | Loading commit data... | |
schedule.rb | Loading commit data... | |
schedule.yml | Loading commit data... | |
secrets.yml.example | Loading commit data... | |
sidekiq.yml.example | Loading commit data... | |
unicorn.rb.example | Loading commit data... | |
unicorn.rb.example.development | Loading commit data... |