- 17 10月, 2016 3 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
- 14 10月, 2016 2 次提交
-
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
-
- 12 10月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 10 10月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This commit introduces a Sidekiq worker that precalculates the list of trending projects on a daily basis. The resulting set is stored in a database table that is then queried by Project.trending. This setup means that Unicorn workers no longer _may_ have to calculate the list of trending projects. Furthermore it supports filtering without any complex caching mechanisms. The data in the "trending_projects" table is inserted in the same order as the project ranking. This means that getting the projects in the correct order is simply a matter of: SELECT projects.* FROM projects INNER JOIN trending_projects ON trending_projects.project_id = projects.id ORDER BY trending_projects.id ASC; Such a query will only take a few milliseconds at most (as measured on GitLab.com), opposed to a few seconds for the query used for calculating the project ranks. The migration in this commit does not require downtime and takes care of populating an initial list of trending projects.
-
- 07 10月, 2016 1 次提交
-
-
由 Nick Thomas 提交于
This commit adds a number of _html columns and, with the exception of Note, starts updating them whenever the content of their partner fields changes. Note has a collision with the note_html attr_accessor; that will be fixed later A background worker for clearing these cache columns is also introduced - use `rake cache:clear` to set it off. You can clear the database or Redis caches separately by running `rake cache:clear:db` or `rake cache:clear:redis`, respectively.
-
- 06 10月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 27 9月, 2016 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 23 9月, 2016 1 次提交
-
-
由 Ahmad Sherif 提交于
-
- 22 9月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
It seems this wasn't updated properly when migrations were added in a previous commit.
-
- 20 9月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
-
- 19 9月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 16 9月, 2016 2 次提交
-
-
由 Drew Blessing 提交于
-
由 Patricio Cano 提交于
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
-
- 15 9月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
1. These changes bring down page load time for 100 issues from more than a minute to about 1.5 seconds. 2. This entire commit is composed of these types of performance enhancements: - Cache relevant data in `IssueMetrics` wherever possible. - Cache relevant data in `MergeRequestMetrics` wherever possible. - Preload metrics 3. Given these improvements, we now only need to make 4 SQL calls: - Load all issues - Load all merge requests - Load all metrics for the issues - Load all metrics for the merge requests 4. A list of all the data points that are now being pre-calculated: a. The first time an issue is mentioned in a commit - In `GitPushService`, find all issues mentioned by the given commit using `ReferenceExtractor`. Set the `first_mentioned_in_commit_at` flag for each of them. - There seems to be a (pre-existing) bug here - files (and therefore commits) created using the Web CI don't have cross-references created, and issues are not closed even when the commit title is "Fixes #xx". b. The first time a merge request is deployed to production When a `Deployment` is created, find all merge requests that were merged in before the deployment, and set the `first_deployed_to_production_at` flag for each of them. c. The start / end time for a merge request pipeline Hook into the `Pipeline` state machine. When the `status` moves to `running`, find the merge requests whose tip commit matches the pipeline, and record the `latest_build_started_at` time for each of them. When the `status` moves to `success`, record the `latest_build_finished_at` time. d. The merge requests that close an issue - This was a big cause of the performance problems we were having with Cycle Analytics. We need to use `ReferenceExtractor` to make this calculation, which is slow when we have to run it on a large number of merge requests. - When a merge request is created, updated, or refreshed, find the issues it closes, and create an instance of `MergeRequestsClosingIssues`, which acts as a join model between merge requests and issues. - If a `MergeRequestsClosingIssues` instance links a merge request and an issue, that issue closes that merge request. 5. The `Queries` module was changed into a class, so we can cache the results of `issues` and `merge_requests_closing_issues` across various cycle analytics stages. 6. The code added in this commit is untested. Tests will be added in the next commit.
-
- 14 9月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This moves tracking of the pushes since the last Git GC from PostgreSQL to Redis. This reduces the number of writes on the "projects" table. This in turn reduces the vacuuming overhead. The lease used for incrementing the counter has been removed. This lease was mostly put in place to prevent high database load but this isn't needed anymore due to the counter now being stored in Redis. Fixes gitlab-org/gitlab-ce#22125
-
- 13 9月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 08 9月, 2016 1 次提交
-
-
由 Stan Hu 提交于
-
- 06 9月, 2016 2 次提交
-
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
-
- 05 9月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 02 9月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 01 9月, 2016 4 次提交
-
-
由 Felipe Artur 提交于
-
-
-
-
- 31 8月, 2016 4 次提交
-
-
由 Stan Hu 提交于
Closes #21678
-
由 Patricio Cano 提交于
-
由 Patricio Cano 提交于
-
由 Valery Sizov 提交于
-
- 27 8月, 2016 1 次提交
-
-
由 Z.J. van de Weg 提交于
These tables, web hooks and services, are unused but where not dropped with the commits d5c91bb9 and 2988e1fb. The file was left too, but never called.
-
- 26 8月, 2016 4 次提交
-
-
由 Timothy Andrew 提交于
-
由 Timothy Andrew 提交于
1. Record the `wip_flag_first_removed_at` and `first_assigned_to_user_other_than_author` metrics for a merge request. Use a `merge_request_metrics` table, similar to the one for `issues`. Metrics are recorded `after_save`. 2. Move larger queries to a `CycleAnalytics::Queries` module.
-
由 Timothy Andrew 提交于
- And store the `first_associated_with_milestone_at` and `first_added_to_board_at` times, when an issue is saved.
-
由 Stan Hu 提交于
Closes #21465 It appears this column was mistakenly omitted in !5623 due to rebasing issues in earlier comments.
-
- 23 8月, 2016 2 次提交
-
-
由 Stan Hu 提交于
In some cases, the artificial 255-character limit would cause an error in MergeWorker. Closes #20593
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 22 8月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-