# Current situation with garbage collection

**URL:** <https://forum.storj.io/t/current-situation-with-garbage-collection/25711>\
**Category:** Node Operators\
**Tags:** garbage-collector, storagenode\
**Created:** [April 2, 2024, 4:47pm UTC](https://forum.storj.io/t/current-situation-with-garbage-collection/25711 "2024-04-02T16:47:47Z")\
**Posts on this page:** 1\
**Showing post:** 285

<div class="post-metadata">

**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\
**Post date:** [April 25, 2024, 2:39pm UTC](https://forum.storj.io/t/current-situation-with-garbage-collection/25711/285 "2024-04-25T14:39:09Z")

</div>

> [@Ambifacient](#):
>
> Double EU1 garbage collection this week?

Yep, after some code optimization – to make the generation faster – we started generating 10 Mbyte bloom filters. EU1 filters are sent out during the last night, AP1 are under sending… Big node operators receive them only with nodes \>=v1.100.

Next round will be generating a 4Mbyte US1, just to make sure that everybody receives at least one filter (even if they use older nodes).

After 4Mbyte US1, we will start generating 10 Mbyte. Exact testing method (sending out one by one or in one batch?) is still under discussion.

ps: yes we use one big machine for BF generation, yes everything in memory, yes we added more resources

ps2: I updated [Storagenode Operational updates](https://forum.storj.io/t/storagenode-operational-updates/25843)

---

_[View the full topic](https://forum.storj.io/t/current-situation-with-garbage-collection/25711)._