Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2023-05-16 | 2 | -73/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-12-05 | 1 | -3/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-11-15 | 1 | -0/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-11-14 | 1 | -0/+17 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-09-01 | 1 | -0/+5 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-07-01 | 1 | -4/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-03-09 | 1 | -16/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-26 | 1 | -3/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-21 | 1 | -34/+0 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-05-19 | 2 | -17/+9 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-04-26 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-02-01 | 1 | -7/+23 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-01-27 | 1 | -0/+4 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-10-15 | 1 | -2/+2 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-22 | 1 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-17 | 1 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-11 | 1 | -3/+3 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-14 | 1 | -2/+11 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-11-07 | 1 | -23/+38 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-30 | 3 | -8/+27 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-16 | 3 | -12/+94 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-10-04 | 1 | -2/+5 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-27 | 1 | -8/+6 |
| | |||||
* | Remove worker label from puma terminations metric65278-fix-puma-master-counter-wipe | Aleksei Lipniagov | 2019-08-12 | 1 | -3/+1 |
| | |||||
* | Run do_master_restart callback on server start | Jan Provaznik | 2019-07-01 | 1 | -0/+3 |
| | | | | | | | | | | We want to call master_restart callback on start too - this callback is used for cleaning up prometheus files. It has been added to Omnibus already: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3350 So make sure that Unicorn example configs are up-to-date and that the same callback is called for Puma too. | ||||
* | Monitor only final statesrack-timeout-rename | Jan Provaznik | 2019-06-12 | 1 | -1/+4 |
| | | | | | | There is no reason to monitor transition states so we ignore ready and active states. We can get ratio of completed vs failed requests from final states. | ||||
* | Moved RackTimeout observer to a different location | Jan Provaznik | 2019-06-12 | 1 | -0/+48 |
| | | | | | Because there will be similar observer for PumaWorkerKiller, it makes sense to keep both on better place. | ||||
* | Add metric for measuring PumaWorkerKiller activity | Jan Provaznik | 2019-06-10 | 2 | -0/+27 |
| | | | | | | PumaWorkerKiller is used for periodically checking and killing workers (the biggest one) if overall memory reaches specified limit. This metric allows us to watch number of killed workers. | ||||
* | Add Puma sampler | Jan Provaznik | 2019-05-29 | 1 | -0/+8 |
| | | | | | This sampler gathers Puma-specific metrics which can be used by Prometheus then. | ||||
* | Reserve more RAM for master process in Pumash-bump-puma-memory-limits | Stan Hu | 2018-11-01 | 1 | -1/+5 |
| | | | | | | The Puma Worker Killer checks the total RAM used by both the master and worker processes. Bump the limits to N+1 instead of N workers to account for this. | ||||
* | Add experimental support for Pumaan-multithreading | Andrew Newdigate | 2018-10-25 | 2 | -0/+131 |
This allows us (and others) to test drive Puma without it affecting all users. Puma can be enabled by setting the environment variable "EXPERIMENTAL_PUMA" to a non empty value. |