• zachatrocity@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Woah nice find. This is outta control. I think our new infinite scroll library will make this better. That should be in the next release and I’ll personally keep a close eye on this. Pretty wild. Thanks for reporting!

  • db2@lemmy.one
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Just checked mine, 1.6 gigs of cache. Anything over a couple hundred megs is extreme.

  • Cheesebaron@feddit.dk
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    LRU cache seems like a good choice for caching images. Then set a max size and/or age of items in the cache and evict as necessary. This is the defacto caching mechanism in Apps.

    • ඞmir@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I don’t like every app having its own max size, I’d hope Android at some point starts making an automatic cache control tool system-wide (that’s not a third party app) but it seems we’re stuck with this mechanism

      • Cheesebaron@feddit.dk
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        It is a bit of wishful thinking, but could be cool if they had an AndroidX package with some kind of global caching system. Problem is though, how do you make a caching mechanism that can fit all use cases.

        • ඞmir@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Start with LRU and maybe a frequency counter to keep frequently useful data. Then go from there. Same as most apps do themselves right now but redistribute as needed; slowly take a bit away from all other apps when one app needs more