Analyze Redis usage in Package related areas
Description
In our effort to improve Redis usage (gitlab-com/www-gitlab-com#4747 (closed)) as soon as possible we are also undertaking dedicated investigations per area to identify non-performant redis usage. Please dedicate 1-2 engineers from your team to go through in an investigative way through the different features of your area. The idea is to have issues at the end with specific severity and if possible some sort of effort estimation (to identify low hanging fruits)
Possible targets for investigation:
- Excessive calls
- Duplicate calls against Redis for the same value on the same request
- Slow calls
- Values that are too big stored in redis which might lockup during write
Good bundled information can be found here - gitlab-com/www-gitlab-com#4747 (comment 188806383)
Investigation
Feature | Redis used? | Problematic? | Comments |
---|---|---|---|
Container Registry | Yes | No | The API uses ExclusiveLeaseGuard to prevent users from making the same request multiple times, not a large Redis load. |
NPM Registry | No | No | |
Maven Registry | No | No | |
Dependency Proxy | No | No |
Conclusion
After investigating, we've determined that the Package code is not contributing to redis load. As we're adding code to our we are keeping load on redis in mind in future development.