Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ci | ||
gitlab | ||
migrate | ||
.gitkeep | ||
brakeman.rake | ||
cache.rake | ||
dev.rake | ||
flay.rake | ||
flog.rake | ||
grape.rake | ||
rubocop.rake | ||
services.rake | ||
setup.rake | ||
sidekiq.rake | ||
spec.rake | ||
spinach.rake | ||
test.rake |
BigW Consortium Gitlab
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.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ci | Loading commit data... | |
gitlab | Loading commit data... | |
migrate | Loading commit data... | |
.gitkeep | Loading commit data... | |
brakeman.rake | Loading commit data... | |
cache.rake | Loading commit data... | |
dev.rake | Loading commit data... | |
flay.rake | Loading commit data... | |
flog.rake | Loading commit data... | |
grape.rake | Loading commit data... | |
rubocop.rake | Loading commit data... | |
services.rake | Loading commit data... | |
setup.rake | Loading commit data... | |
sidekiq.rake | Loading commit data... | |
spec.rake | Loading commit data... | |
spinach.rake | Loading commit data... | |
test.rake | Loading commit data... |