Save quick cache to disk

[joanbalaguero]

Hi Arthur,

Here trying to serialize to disk a quick cache (that can hold up to 64GB of data) to disk.

My first approach was having an iterator over the non expired entries and just save them to disk, this is quite slow.

So, as a creator of this crate, I was wondering if you could advise me about any other way to do this, maybe starting several threads and reading, at the same time, different parts of the cache.

Not sure, I'm relatively new to rust, if you can have an idea about the best way to do this serialization then fantastic, otherwise I will continue trying other ways.

Thanks!

Joan.

[arthurprs]

I assume you only do this occasionally as some sort of backup?

If so, we can look into providing a rayon iterator compatibility so you can parallelize it easily.

[joanbalaguero]

Hi Arthur, Yes, that’s exactly the case. I suppose this must be a common case, having an in-memory cache and, at any moment, you need to stop it because of an app or server upgrade, so you want to backup all data and then restore it when the app starts again. I already implemented it (backup and restore) for my case, but just using an iterator over all the entries, using parallelism with Rayon is, unfortunately, far away from my rust knowledge right now. If you think this can be useful I can open a PR, and if you need anything from me, just let me know ! Thanks and again congrats for this amazing crate, Joan. From: Arthur Silva ***@***.***> Sent: Wednesday, September 3, 2025 11:43 PM To: arthurprs/quick-cache ***@***.***> Cc: joanbalaguero ***@***.***>; Author ***@***.***> Subject: Re: [arthurprs/quick-cache] Save quick cache to disk (Issue #79) <https://avatars.githubusercontent.com/u/715958?s=20&v=4> arthurprs left a comment (arthurprs/quick-cache#79) <#79 (comment)> I assume you only do this occasionally as some sort of backup? If so, we can look into providing a rayon iterator <https://github.com/rayon-rs/rayon> compatibility so you can parallelize it easily. — Reply to this email directly, view it on GitHub <#79 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAXLWA7DHADGV3WV2RHCR33Q5OG7AVCNFSM6AAAAACFP7MZPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJQHEYTCNZWGM> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/ACAXLWHF7SRZWI4ADJEQM3L3Q5OG7A5CNFSM6AAAAACFP7MZPGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTWBYT5BG.gif> Message ID: ***@***.*** ***@***.***> >

[praveenperera]

I'm doing this by saving the path as the value and hooking it up to the lifecycle to delete from disk when its evicted.

I have a small RAM cache and a larger FileCache.