Big sorted sets in redis for Elastic bookkeeping (#244865) · Issues · GitLab.org / GitLab · GitLab (original) (raw)

Skip to content

GitLab Next

• • Why GitLab
  • Pricing
  • Contact Sales
  • Explore
• Why GitLab
• Pricing
• Contact Sales
• Explore
• Sign in
• Get free trial

Big sorted sets in redis for Elastic bookkeeping

ZREMRANGEBYSCORE shows up in our Redis slowlogs for both of these sets:

1. elastic:incremental:updates:0:zset
2. elastic:bulk:initial:0:zset

At the time of writing, the timings are slow-but-not-terrible:

https://log.gprd.gitlab.net/goto/77a9ef51ad1ecfe373a812ec738c53c4

We should still investigate as this might get slower as the set size increases.

The set for the bulk:initial bookkeeping also shows up in the big key reports (gitlab-com/gl-infra/scalability#500).

Edited Sep 04, 2020 by Bob Van Landuyt