Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-07-20 | Add latest changes from gitlab-org/gitlab@15-2-stable-eev15.2.0-rc42 | GitLab Bot | |
2022-06-20 | Add latest changes from gitlab-org/gitlab@15-1-stable-eev15.1.0-rc42 | GitLab Bot | |
2022-04-20 | Add latest changes from gitlab-org/gitlab@14-10-stable-eev14.10.0-rc42 | GitLab Bot | |
2022-03-18 | Add latest changes from gitlab-org/gitlab@14-9-stable-eev14.9.0-rc42 | GitLab Bot | |
2022-02-18 | Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42 | GitLab Bot | |
2021-11-18 | Add latest changes from gitlab-org/gitlab@14-5-stable-eev14.5.0-rc42 | GitLab Bot | |
2021-10-20 | Add latest changes from gitlab-org/gitlab@14-4-stable-eev14.4.0-rc42 | GitLab Bot | |
2021-09-20 | Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42 | GitLab Bot | |
2021-08-19 | Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42 | GitLab Bot | |
2021-07-20 | Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42 | GitLab Bot | |
2021-06-17 | Add latest changes from gitlab-org/gitlab@14-0-stable-ee | GitLab Bot | |
2021-06-16 | Add latest changes from gitlab-org/gitlab@14-0-stable-eev14.0.0-rc42 | GitLab Bot | |
2021-04-21 | Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43 | GitLab Bot | |
2021-03-16 | Add latest changes from gitlab-org/gitlab@13-10-stable-eev13.10.0-rc40 | GitLab Bot | |
2021-02-18 | Add latest changes from gitlab-org/gitlab@13-9-stable-eev13.9.0-rc42 | GitLab Bot | |
2021-01-20 | Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42 | Robert Speicher | |
2020-12-17 | Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42 | GitLab Bot | |
2020-11-19 | Add latest changes from gitlab-org/gitlab@13-6-stable-eev13.6.0-rc42 | GitLab Bot | |
2020-10-21 | Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42 | GitLab Bot | |
2020-09-19 | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | |
2020-07-20 | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | |
2020-06-18 | Add latest changes from gitlab-org/gitlab@13-1-stable-ee | GitLab Bot | |
2020-05-20 | Add latest changes from gitlab-org/gitlab@13-0-stable-ee | GitLab Bot | |
2020-03-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-05 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-26 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-25 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-08-08 | Disable vue-i18n for non-autofix files | Ezekiel Kigbo | |
Disables the vue-i18n eslint rules for files that are not able to be autofixed, this will stop these offences causing pipeline failures but they will need manual fixing. | |||
2019-08-06 | Remove GC metrics from performance bar | Sean McGivern | |
These were disabled in production mode, but that also broke the rest of the performance bar. As they were only enabled in development mode, we can just remove them for now. | |||
2019-08-02 | Fix performance bar warnings when Rugged is disabled | Stan Hu | |
`detailed_metric.vue` was attempting to read the `duration` field even when the metric did not exist in the JSON payload. We now check for the existence of the metrics before attempting to display the value. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65491 | |||
2019-07-30 | Remove line profiler from performance bar | Sean McGivern | |
1. The output isn't great. It can be hard to find hotspots and, even when you do find them, to find why those are hotspots. 2. It uses some jQuery-specific frontend code which we can remove now that we don't have this any more. 3. It's only possible to profile the initial request, not any subsequent AJAX requests. | |||
2019-07-26 | Replace peek-pg with our own implementation | Sean McGivern | |
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-25 | Autofix i18n lints for vue files | Ezekiel Kigbo | |
Autofixes additional linting errors found in vue files. | |||
2019-07-24 | Add Rugged calls to performance bar | Stan Hu | |
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-03 | Add Redis call details in Peek performance bar | Stan Hu | |
Since Redis timings appear to be increasing in production, this change makes it easier to see what exactly which queries are being called and where. This is done by prepending modules in peek-redis to store the call details. This commit redact values for all SET commands (e.g. HMSET, GETSET, etc.). | |||
2019-06-28 | Namespace performance bar translations | Ezekiel Kigbo | |
Added additional translations | |||
2019-06-27 | Vue-i18n: app/assets/javascripts/performance_bar/ directory | Ezekiel Kigbo | |
i18n linting for .vue files under the app/assets/javascripts/performance_bar/ directory | |||
2019-04-17 | Merge branch 'sh-add-gitaly-backtrace' into 'master' | Sean McGivern | |
Add backtrace to Gitaly performance bar Closes #60092 See merge request gitlab-org/gitlab-ce!27345 | |||
2019-04-17 | Add backtrace to Gitaly performance bar | Stan Hu | |
This adds the backtrace to a table to show exactly where the Gitaly call was made to make it easier to understand where the call originated. This change also collapses the details in the same row to improve the usability when there is a backtrace. | |||
2019-04-16 | Add QA tests for the performance bar | Sean McGivern | |
These are very high-level. Currently, they test: 1. That the performance bar appears. 2. That it has detailed metrics for Postgres and Gitaly. 3. That AJAX requests are included in the request selector. | |||
2019-02-08 | Provide a performance bar link to the Jaeger UI | Andrew Newdigate | |
Jaeger is a distributed tracing tool. This change adds a "Tracing" link to the performance bar to directly link to a current request in Jaeger. This is useful for two reasons: 1 - it provides affordance to developers that the distributed tracing tool is available, so that it can quickly be discovered. 2 - it allows developers to quickly find a specific trace without having to manually navigate to a second user-interface. | |||
2018-11-27 | Replace `=== true` with `parseBoolean()` | Winnie Hellmann | |
2018-11-20 | Prettify all the things | Mike Greiling | |
2018-10-17 | Prettify performance_bar notes and profile modules | Mike Greiling | |