kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/config/initializers/peek.rb

16 lines
585 B
Ruby
Raw Normal View History

Replace peek-pg with our own implementation This uses an ActiveRecord subscriber to get queries and calculate the total query time from that. This means that the total will always be consistent with the queries in the table. It does however mean that we could potentially miss some queries that don't go through ActiveRecord. Making this change also allows us to unify the response JSON a little bit, making the frontend slightly simpler as a result.
2019-07-26 09:03:00 -04:00
require 'peek/adapters/redis'
Adds Rubocop rule for line break around conditionals
2018-01-11 11:34:01 -05:00
Replace peek-pg with our own implementation This uses an ActiveRecord subscriber to get queries and calculate the total query time from that. This means that the total will always be consistent with the queries in the table. It does however mean that we could potentially miss some queries that don't go through ActiveRecord. Making this change also allows us to unify the response JSON a little bit, making the frontend slightly simpler as a result.
2019-07-26 09:03:00 -04:00
Peek::Adapters::Redis.prepend ::Gitlab::PerformanceBar::RedisAdapterWhenPeekEnabled
Add top-level warnings key to performance bar response This key is useful to reduce the amount of logic needed on the frontend: if `has_warnings` is true, then the frontend knows that the request in question has warnings for some metric.
2019-08-23 08:05:38 -04:00
Peek.singleton_class.prepend ::Gitlab::PerformanceBar::WithTopLevelWarnings
Include all queries in the performance bar summary Rails 5.1's `exec_no_cache` doesn't call `async_exec` any more, but `exec_params`: https://github.com/rails/rails/pull/33188 This means that the DB summary in the performance bar was wrong. The individual query details were still correct (we subscribe to ActiveRecord events for those). We can remove this once the upstream PR to peek-pg is in a release and we update to use that release.
2019-05-03 07:31:01 -04:00
Replace peek-pg with our own implementation This uses an ActiveRecord subscriber to get queries and calculate the total query time from that. This means that the total will always be consistent with the queries in the table. It does however mean that we could potentially miss some queries that don't go through ActiveRecord. Making this change also allows us to unify the response JSON a little bit, making the frontend slightly simpler as a result.
2019-07-26 09:03:00 -04:00
Rails.application.config.peek.adapter = :redis, { client: ::Redis.new(Gitlab::Redis::Cache.params) }
Adds Rubocop rule for line break around conditionals
2018-01-11 11:34:01 -05:00
Replace peek-pg with our own implementation This uses an ActiveRecord subscriber to get queries and calculate the total query time from that. This means that the total will always be consistent with the queries in the table. It does however mean that we could potentially miss some queries that don't go through ActiveRecord. Making this change also allows us to unify the response JSON a little bit, making the frontend slightly simpler as a result.
2019-07-26 09:03:00 -04:00
Peek.into Peek::Views::Host
Peek.into Peek::Views::ActiveRecord
Make Gitaly more prominent in the performance bar This is as important as SQL timings, and much more important most of the time than GC, Redis, or Sidekiq.
2018-03-08 04:58:24 -05:00
Peek.into Peek::Views::Gitaly
Fix inconsistency in Redis performance bar stats peek-redis resets its counters at the start of an ActionController notification (`start_processing.action_controller`), which causes it to miss some Redis queries that precede it, such as the database load balancer and Rack Attack queries. This produces inconsistencies in the performance bar between the number of calls and their durations with the actual calls in the detailed view. We fix this by getting rid of peek-redis in favor of consolidating all logic into the `RedisDetailed` view, which tracks Redis queries using `RequestStore`. This has the nice property of removing thread-specific counters as well. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64707
2019-07-17 15:33:49 -04:00
Peek.into Peek::Views::RedisDetailed
Add Rugged calls to performance bar This will help diagnose the source of excessive I/O from Rugged calls. To implement this, we need to obtain the full list of arguments sent to each request method.
2019-07-21 01:34:46 -04:00
Peek.into Peek::Views::Rugged
Add latest changes from gitlab-org/gitlab@master
2020-05-21 20:08:07 -04:00
Peek.into Peek::Views::BulletDetailed if defined?(Bullet)
Call `GC::Profiler.clear` only in one place Previously, both InfluxSampler and RubySampler were relying on the `GC::Profiler.total_time` data which is the sum over the list of captured GC events. Also, both samplers asynchronously called `GC::Profiler.clear` which led to incorrect metric data because each sampler has the wrong assumption it is the only object who calls `GC::Profiler.clear` and thus could rely on the gathered results between such calls. We should ensure that `GC::Profiler.total_time` is called only in one place making it possible to rely on accumulated data between such wipes. Also, we need to track the amount of profiler reports we lost.
2019-08-02 05:04:32 -04:00
Migrate correlation and tracing code to LabKit This change is a fairly straightforward refactor to extract the tracing and correlation-id code from the gitlab rails codebase into the new LabKit-Ruby project. The corresponding import into LabKit-Ruby was in https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1 The code itself remains very similar for now. Extracting it allows us to reuse it in other projects, such as Gitaly-Ruby. This will give us the advantages of correlation-ids and distributed tracing in that project too.
2019-02-18 15:57:22 -05:00
Peek.into Peek::Views::Tracing if Labkit::Tracing.tracing_url_enabled?
Copy permalink