# Uso inusualmente alto de la caché de Service Worker

**URL:** <https://meta.discourse.org/t/unusually-large-service-worker-cache-usage/166801>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [9 Octubre, 2020 20:58 UTC](https://meta.discourse.org/t/unusually-large-service-worker-cache-usage/166801 "2020-10-09T20:58:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [9 Octubre, 2020 21:00 UTC](https://meta.discourse.org/t/unusually-large-service-worker-cache-usage/166801/2 "2020-10-09T21:00:59Z")

</div>

Desafortunadamente, esto es una peculiaridad de cómo Chrome informa el uso de la caché. El espacio reportado no refleja con precisión el espacio utilizado en el disco. Estamos trabajando en algunas mejoras para solucionar el problema, pero aún no están listas. Puedes encontrar más información aquí:

> [@High local storage reported by Chrome](https://meta.discourse.org/t/high-local-storage-reported-by-chrome/165233/2?u=david):
>
> This is a know Chrome quirk where it misreports by a lot (100MB may be reported as 5GB). We are actively working on ways to mitigate this issue as we get frequent reports, but it is quite complicated as it involves assets served from CDNs. You can read more about it in

---

_[View the full topic](https://meta.discourse.org/t/unusually-large-service-worker-cache-usage/166801)._