Welcome! Log In Create A New Profile

Advanced

Inner workings of nginx cache manager

Stefan Safar
November 29, 2018 09:24AM
Hi there,

I'd like to know a little bit more about the inner workings of the cache
manager. I looked through the code, and if I understand it correctly, when
it runs out of disk space specified by max_size, it tries to run the cache
manager, which looks at a queue of last-accessed URLs and tries to remove
the least used URL from the queue and from the disk.

My question is, whether the queue is somehow persisted on disk, or I
misunderstood something? What I'm trying to know is what happens when an
nginx instance runs out of disk space and it's restarted - how does nginx
know what it should or shouldn't delete? I don't think I saw any code that
would scan through the disk and that would be a rather slow way to deal
with this.

Thanks,

Stefan Safar
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Inner workings of nginx cache manager

Stefan Safar November 29, 2018 09:24AM

Re: Inner workings of nginx cache manager

Maxim Dounin November 29, 2018 09:52AM

Re: Inner workings of nginx cache manager

Stefan Safar November 30, 2018 07:28AM

Re: Inner workings of nginx cache manager

Maxim Dounin November 30, 2018 08:00AM

Re: Inner workings of nginx cache manager

Stefan Safar November 30, 2018 08:06AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 78
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready