An error occurred fetching the project authors.
- 03 Feb, 2022 1 commit
-
-
Matthias Käppler authored
This change captures and emits the time it takes for the primary Rails process to start up. - Log it to application JSON log - Emit it to prometheus - Print it to the console message This is only active for Puma, Sidekiq and Rails console. Changelog: added
-
- 27 Oct, 2021 1 commit
-
-
Heinrich Lee Yu authored
This also mounts the Action Cable engine all the time. Mounting the engine has minimal impact on memory so we should just mount it all the time to reduce configuration complexity. Changelog: added
-
- 20 Oct, 2021 1 commit
-
-
Heinrich Lee Yu authored
This retrieves jobs from Sidekiq scheduled sets using a Lua script. This allows multiple processes to process the queue efficiently.
-
- 19 May, 2021 1 commit
-
-
Aleksei Lipniagov authored
Updates specs which are do not directly related the Unicorn-related classes which are planned to be removed. This is assumed to be a safe change, as it is spec-only, so should be easily validated via CI. Split from https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61888.
-
- 11 May, 2021 1 commit
-
-
Thong Kuah authored
Fix max_threads for Puma with no cli_config
-
- 12 Feb, 2021 1 commit
-
-
Aleksei Lipniagov authored
Introduces `puma_in_clustered_mode?` check. Introduces `.available?` for health checks. Sets MasterCheck as not available for Puma in a Single mode.
-
- 07 Jul, 2020 1 commit
-
-
Heinrich Lee Yu authored
This is going to be used early when computing Runtime.max_threads so we can't use gitlab.yml to store these.
-
- 03 Jul, 2020 1 commit
-
-
Heinrich Lee Yu authored
This reverts merge request !34291
-
- 23 Jun, 2020 1 commit
-
-
Arturo Herrero authored
The plan for RSpec 4.0 is to disable monkey patching, reference: https://rspec.info/blog/2013/07/the-plan-for-rspec-3/#zero-monkey-patching-mode https://relishapp.com/rspec/rspec-core/docs/configuration/zero-monkey-patching-mode This commit stops using RSpec monkey patching in several specs.
-
- 10 Jun, 2020 1 commit
-
-
Heinrich Lee Yu authored
This reverts merge request !33943
-
- 09 Jun, 2020 1 commit
-
-
Heinrich Lee Yu authored
Adds an option in gitlab.yml to run ActionCable in in-app mode Connection pool settings are also adjusted to account for the extra threads
-
- 03 May, 2020 1 commit
-
-
Heinrich Lee Yu authored
Use ActionCable's worker pool size to determine connection pool size
-
- 17 Feb, 2020 1 commit
-
-
Bob Van Landuyt authored
This adds the threads we know are running next to the worker threads for Puma and Sidekiq. Adding them here makes sure our connection pool for the database is large enough. In puma, the main thread also connects to the database, so we need to count that. In Sidekiq, the main thread and the poller for Sidekiq cron could also connect to the database.
-
- 15 Feb, 2020 1 commit
-
-
DJ Mountney authored
Otherwise users get runtime identification errors when omnibus-gitlab adds instance level apps for auth, like grafana and mattermost.
-
- 06 Feb, 2020 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 31 Jan, 2020 1 commit
-
-
Matthias Kaeppler authored
The problem was that when running under `spring`, the process name is not `rspec` anymore. I think we don't need to test the process name anyway, we can instead rely on just `Rails.env`.
-
- 15 Jan, 2020 1 commit
-
-
Matthias Kaeppler authored
This merges settings from the existing initializer and the sidekiq initializer into a single file. Logs any forced increases in db pool size.
-
- 27 Dec, 2019 1 commit
-
-
Stan Hu authored
Previously the runtime detector would flag a `RUNTIME IDENTIFICATION FAILED` warning if application.log if rspec or rake were used. This change also removes the unnecessary log message. Closes https://gitlab.com/gitlab-org/gitlab/issues/122656
-
- 20 Dec, 2019 4 commits
-
-
Matthias Kaeppler authored
Turns out this is actually necessary in some places
-
Matthias Kaeppler authored
- don't allow `:unknown` runtime, raise error instead - log errors to Sentry in initializer
-
Matthias Kaeppler authored
-
Matthias Kaeppler authored
This reverts commit b0944b95.
-
- 16 Dec, 2019 1 commit
-
-
Michael Kozono authored
This reverts merge request !20294
-
- 11 Dec, 2019 1 commit
-
-
Matthias Käppler authored
This will serve as the new single access point into identifying which runtime is active. Add Process.max_threads method This will return the maximum concurrency for the given runtime environment. Revert to including `defined?` checks for Process This is based on a reference impl by new relic which they use to detect the current dispatcher. Add `name` method, throw if ambiguous This can be called from an initializer for instance. Log the current runtime in an initializer Add `multi_threaded?` and `app_server?` helpers To allow easier grouping of configuration Rename `Process` to `Runtime` And move it into its own file. Replace all remaining runtime checks with new API Including a commit body because the danger bot politely asked me to. There really is nothing else to say. Prefer `class << self` over `instance_eval` It seems to be the more widely adopted style. Simplify `has_instances?` helper method Fix rubocop offense Remove max_threads method This wasn't currently used anywhere and we should define this elsewhere. Remove references to NR library This caused some legal questions. We weren't using the instance lookup before, so it should be OK.
-