New answers tagged cache
Nope nope nope! This is not how it is done. Linux (the kernel) can choose to put some files in the cache and to remove them whenever it wants. You really can't be sure that anything is in the cache or not. And this command won't change that (a lot). The advice in the link you provided is so wrong in so many ways! The cache is an OS thing. You don't need ...
Route Cache and Neighbor Tables are somewhat similar in that they both help decide where to send a packet next. The difference is the Neighbor Table caches entries at the layer 2 (ethernet) level; it helps translate IP addresses into MAC addresses. The ARP protocol is used to query for new entries to cache. A Route Cache works at layer 3 (IP). The ...
There is /dev/shm, which is a RAM-backed filesystem. This isn't the same as caching as a cache means the file also resides on disk. With /dev/shm, which is a tmpfs filesystem, the files exist in memory only. Note that you can mount tmpfs volumes anywhere: mount -t tmpfs none /foo/bar There is just one usually mounted at /dev/shm.
After much research and reading this great article I found temporary solutions: decreasing net.ipv4.route.gc_timeout so the entries from cache get removed faster, and increasing net.ipv4.route.gc_interval so the garbage collector runs more often. But these are all temporary, since on our machine it only solved the problem for a few hours and more intensive ...
Top 50 recent answers are included