# Badger cache: are we ready?

**URL:** <https://forum.storj.io/t/badger-cache-are-we-ready/27323>\
**Category:** Node Operators\
**Tags:** badger\
**Created:** [July 28, 2024, 9:41am UTC](https://forum.storj.io/t/badger-cache-are-we-ready/27323 "2024-07-28T09:41:48Z")\
**Posts on this page:** 1\
**Showing post:** 95

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [September 9, 2024, 6:59am UTC](https://forum.storj.io/t/badger-cache-are-we-ready/27323/95 "2024-09-09T06:59:25Z")

</div>

It’s continuous update with each piece requested, if it’s was missing. So, not so much help for deletions, only the stat requests, which are pretty fast anyway for the deletion, but the deletion itself is a slow function on any OS and seems any FS, even with ZFS, see [Unlink performance on FreeBSD](https://forum.storj.io/t/unlink-performance-on-freebsd/27787).

> [@snorkel](#):
>
> Regarding Filewalker, dose it scan only the blobs? Or the trash too?

both. If you would call an endpoint `/mon/ps` on a debug port, you can see that.

---

_[View the full topic](https://forum.storj.io/t/badger-cache-are-we-ready/27323)._