Skip to content

Binary Cache Size Limit #171

Description

@Kruziikrel13

An idea that popped into my head, would define it as a "Nice to Have"

Could also just be a bandaid over a larger problem or maybe I just need to configure garbage collection to be more aggressive or better define my jobsets.


A configuration option to declare a maximum binary cache / database size to prevent the cache from accidentally just building itself into an incidental failure state.

I noticed just having my ci running in the background, and with only a few projects & jobsets it can go from 6GB to 21GB or 32GB... my point being it can fill up QUICK.

As for ideas on how to handle a cache that has hit maximum size...

  1. Notify the user
    • Hey your cache is getting pretty close to full. OR
    • AHHH your cache is full! Handle it!
  2. Automatically run garbage collection at max size to drop packages that are either very old or haven't been fetched in some time.
    • Although this doesn't necessarily guarantee that space will be created.
  3. Stop building (This seems counter-intuitive though)

Give the user a choice between any of the above?

It's not a massive issue that it fills up. And probably the onus lay more on me because I am running a binary cache server on an old laptop with only 500GB storage so the joke is on me but just an idea!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions