| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Put CACHE_NAMESPACE in the Gitlab::Redis module | Jacob Vosmaer | 2016-04-07 | 1 | -1/+1 |
| | | |||||
| * | Add Gitlab::Redis connection pool | Jacob Vosmaer | 2016-04-04 | 1 | -12/+13 |
| | | |||||
| * | Parse config/resque.yml in one place only | Jacob Vosmaer | 2016-03-09 | 1 | -3/+3 |
| | | |||||
| * | Batch size >1000 does not pay offcomment-batch-size | Jacob Vosmaer | 2016-02-25 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | We did a small experiment to see how a full scan of the Redis keys on gitlab.com speeds up as we increase the batch size. The values on the right are time in seconds for a full scan (no delete operations). count: 10); 284.500529021 count: 100); 86.21216934 count: 1_000); 60.931676195 count: 10_000); 60.96355610 count: 100_000); 62.378172541 It looks like 1,000 is a good number. | ||||
| * | Improve readability of 'rake cache:clear' coderefactor-scan | Jacob Vosmaer | 2016-02-19 | 1 | -6/+5 |
| | | |||||
| * | Use SCAN during 'rake cache:clear'cache-clear | Jacob Vosmaer | 2016-02-18 | 1 | -4/+15 |
| | | | | | | | This allows 'rake cache:clear' to delete millions of keys without choking. It requires Redis 2.8.0 or newer but we needed that already anyway. | ||||
| * | Replace GITLAB with GitLab in rake task descriptions | Dmitriy Zaporozhets | 2015-06-23 | 1 | -1/+1 |
| | | |||||
| * | Patch `rake cache:clear` for large amounts of keys | Jacob Vosmaer | 2014-06-20 | 1 | -1/+6 |
| | | |||||
| * | rake task to clear redis cache | Dmitriy Zaporozhets | 2013-03-31 | 1 | -0/+6 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |