Support Disk Cache Warming
See original GitHub issuefetch() with no callback coupled with skipCache(). Should not do any bitmap decoding and it should abandon the hold on the connection as soon as possible.
Issue Analytics
- State:
- Created 10 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Disk Cache Warming Guide | ObjectiveFS
You can warm the disk cache by prefetching file metadata in commonly used directories after your filesystem is mounted. Example command to ...
Read more >Caching: Cold Cache Vs. Warm Cache - Baeldung
In this tutorial, we'll investigate cold and warm caches. Our objective is to understand the main differences and potential consequences of ...
Read more >Cache warming: Leveraging EBS for moving petabytes of data
We had previously given an overview of how we perform cache warming on our EVCache clusters and why it's needed.
Read more >Cache Warming - Qlik Sense Admin Playbook
Cache Warming in Qlik Sense Enterprise refers to programmatically opening Qlik applications so that the base application is preloaded into RAM before users ......
Read more >Optimize performance with caching on Databricks
When the disk cache is enabled, data that has to be fetched from a remote source is automatically added to the cache. This...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Any update to this issue? I need to pre-fetch about 500 images and
fetch()is unnecessarily decoding each one. Also, it appears thatskipCache()has been replaced by something else. Not sure what though.I’ve had a root around and it looks like adding:
to
BitmapHunter.hunt()beforedecodeStream()is called does the trick. Memory usage and device load during cache warming (many calls tofetch()) is much lower and the http cache is filled as before.What might I be missing?