- 18 3月, 2016 1 次提交
-
-
- 05 2月, 2016 1 次提交
-
-
由 Josh Frye 提交于
-
- 27 1月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
By simply loading the first event from the already sorted set we save ourselves extra (slow) queries just to get the latest update timestamp. This removes the need for Event.latest_update_time and significantly reduces the time needed to build an Atom feed. Fixes gitlab-org/gitlab-ce#12415
-
- 26 1月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
By instead using a sub-query we save ourselves the overhead of loading any data into memory only to pass it on to another query.
-
- 02 12月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 18 11月, 2015 2 次提交
-
-
由 Yorick Peterse 提交于
This will be used to move some querying logic from the users controller to the Event model (where it belongs).
-
由 Yorick Peterse 提交于
Instead of using MAX(events.updated_at) we can simply sort the events in descending order by the "id" column and grab the first row. In other words, instead of this: SELECT max(events.updated_at) AS max_id FROM events LEFT OUTER JOIN projects ON projects.id = events.project_id LEFT OUTER JOIN namespaces ON namespaces.id = projects.namespace_id WHERE events.author_id IS NOT NULL AND events.project_id IN (13083); we can use this: SELECT events.updated_at AS max_id FROM events LEFT OUTER JOIN projects ON projects.id = events.project_id LEFT OUTER JOIN namespaces ON namespaces.id = projects.namespace_id WHERE events.author_id IS NOT NULL AND events.project_id IN (13083) ORDER BY events.id DESC LIMIT 1; This has the benefit that on PostgreSQL a backwards index scan can be used, which due to the "LIMIT 1" will at most process only a single row. This in turn greatly speeds up the process of grabbing the latest update time. This can be confirmed by looking at the query plans. The first query produces the following plan: Aggregate (cost=43779.84..43779.85 rows=1 width=12) (actual time=2142.462..2142.462 rows=1 loops=1) -> Index Scan using index_events_on_project_id on events (cost=0.43..43704.69 rows=30060 width=12) (actual time=0.033..2138.086 rows=32769 loops=1) Index Cond: (project_id = 13083) Filter: (author_id IS NOT NULL) Planning time: 1.248 ms Execution time: 2142.548 ms The second query in turn produces the following plan: Limit (cost=0.43..41.65 rows=1 width=16) (actual time=1.394..1.394 rows=1 loops=1) -> Index Scan Backward using events_pkey on events (cost=0.43..1238907.96 rows=30060 width=16) (actual time=1.394..1.394 rows=1 loops=1) Filter: ((author_id IS NOT NULL) AND (project_id = 13083)) Rows Removed by Filter: 2104 Planning time: 0.166 ms Execution time: 1.408 ms According to the above plans the 2nd query is around 1500 times faster. However, re-running the first query produces timings of around 80 ms, making the 2nd query "only" around 55 times faster.
-
- 11 11月, 2015 1 次提交
-
-
由 Yorick Peterse 提交于
These scopes can just sort by the "id" column in descending order to achieve the same result. An added benefit is being able to perform a backwards index scan (depending on the rest of the final query) instead of having to actually sort data.
-
- 15 9月, 2015 1 次提交
-
-
由 Stan Hu 提交于
for posterity. Also fix issue where destroying a Milestone would cause odd, transient messages like "created milestone" or "imported milestone". Add "in" preposition when creating and destroying milestones Closes #2382
-
- 02 7月, 2015 1 次提交
-
-
由 catatsuy 提交于
If you are already sorting in descending order in the created_at, it is run twice when you run the .recent. It has passed in the string 'created_at DESC'. Ruby on Rails is directly given to the SQL. It is a slow query in MySQL.
-
- 06 4月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 23 3月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 18 3月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 10 3月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 19 2月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 13 2月, 2015 3 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
Example: "User joined project Namespace / Project" rather than "User joined project at Namespace / Project"
-
由 Douwe Maan 提交于
-
- 06 2月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 29 12月, 2014 1 次提交
-
-
由 Ciro Santilli 提交于
-
- 04 11月, 2014 1 次提交
-
-
由 Ciro Santilli 提交于
-
- 10 10月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 26 7月, 2014 1 次提交
-
-
由 Jeroen van Baarsen 提交于
Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 26 6月, 2014 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 18 6月, 2014 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
- 13 6月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 29 5月, 2014 1 次提交
-
-
由 Kyle Fazzari 提交于
This fixes #305.
-
- 09 4月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 25 3月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 24 2月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Also fixes issue with branch/tag removing via UI Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 10 12月, 2013 1 次提交
-
-
由 Jeroen van Baarsen 提交于
-
- 25 11月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 13 11月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 21 8月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 20 8月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
* call set_iid before validation * make rake task pass event if objects are invalid * show iid in comment event at dashboard
-
由 Dmitriy Zaporozhets 提交于
-
- 17 7月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-