Wasn’t Connect supposed to automatically trim the image cache if it reached a certain size? Something like 5GB should be plenty, I think.

  • kuro@lemmy.caM
    link
    fedilink
    arrow-up
    8
    ·
    14 days ago

    The current caching system is a maximum of 500 objects for up to 14 days. I see your cache includes a lot of mp4s, I think I’ll expose a max cache size as a setting in v296. Cheers!

  • Unforeseen@sh.itjust.works
    link
    fedilink
    arrow-up
    6
    ·
    14 days ago

    I think this would be good as long as it is adjustable so you can pick the size.

    Not everyone has free or unlimited data and I prefer lazy vs aggressive cache trimming.

    • sirxdaemon@lemmy.caOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      14 days ago

      Dev did just that. In v1.296 you can now specify the max cache size. I think 2GB is the default but you can totally up that yourself.

  • remotelove@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    14 days ago

    The files you have cached seem to justify having a large cache size.

    The cache seems like a FIFO buffer, so having a sub-5gb cache might cause excessive loading and reduced battery. (Just speculation though! I have never designed a cache for a phone app before.) Having room for at around 100 items seems logical, and that could potentially need a ton of space for mixed content.