Jacob Vosmaer a310901280 Batch size >1000 does not pay off ...

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.

2016-02-25 13:50:08 +01:00

..

ci

Migrate CI::Project to Project

2015-12-11 18:02:09 +01:00

gitlab

Merge branch 'uploads-700' into 'master'

2016-02-23 15:12:20 +00:00

migrate

Improve performance of User.by_login

2015-10-15 11:58:25 +02:00

.gitkeep

init commit

2011-10-09 00:36:38 +03:00

brakeman.rake

Merge branch 'brakeman-level'

2015-05-12 13:21:11 +03:00

cache.rake

Batch size >1000 does not pay off

2016-02-25 13:50:08 +01:00

dev.rake

Replace GITLAB with GitLab in rake task descriptions

2015-06-23 16:52:40 +02:00

flay.rake

Set higher flay value to avoid unnecessary refactoring for now

2015-11-17 11:18:01 +01:00

flog.rake

Allow flog failure for now

2015-11-11 15:30:23 +01:00

grape.rake

Add grape routing print

2015-11-12 16:26:23 +01:00

rubocop.rake

Dont load rubocop in prod env

2015-02-03 19:25:57 -08:00

services.rake

Added service API endpoint to retrieve service parameters

2015-09-10 18:22:57 +02:00

setup.rake

Replace GITLAB with GitLab in rake task descriptions

2015-06-23 16:52:40 +02:00

sidekiq.rake

Replace GITLAB with GitLab in rake task descriptions

2015-06-23 16:52:40 +02:00

spec.rake

Split up spec:other even more

2015-12-09 11:56:23 +01:00

spinach.rake

Split up feature specs more

2015-12-09 10:50:43 +01:00

test.rake

Use teaspoon instead of jasmine:ci

2015-07-03 10:51:44 +02:00