As part of doing some cold cache timings, I'm trying to free the OS cache. The kernel documentation (retrieved January 2019) says:


Writing to this will cause the kernel to drop clean caches, as well as
reclaimable slab objects like dentries and inodes.  Once dropped, their
memory becomes free.

To free pagecache:
    echo 1 > /proc/sys/vm/drop_caches
To free reclaimable slab objects (includes dentries and inodes):
    echo 2 > /proc/sys/vm/drop_caches
To free slab objects and pagecache:
    echo 3 > /proc/sys/vm/drop_caches

This is a non-destructive operation and will not free any dirty objects.
To increase the number of objects freed by this operation, the user may run
`sync' prior to writing to /proc/sys/vm/drop_caches.  This will minimize the
number of dirty objects on the system and create more candidates to be

This file is not a means to control the growth of the various kernel caches
(inodes, dentries, pagecache, etc...)  These objects are automatically
reclaimed by the kernel when memory is needed elsewhere on the system.

Use of this file can cause performance problems.  Since it discards cached
objects, it may cost a significant amount of I/O and CPU to recreate the
dropped objects, especially if they were under heavy use.  Because of this,
use outside of a testing or debugging environment is not recommended.

You may see informational messages in your kernel log when this file is

    cat (1234): drop_caches: 3

These are informational only.  They do not mean that anything is wrong
with your system.  To disable them, echo 4 (bit 3) into drop_caches.

I'm a bit sketchy about the details. Running

echo 3 > /proc/sys/vm/drop_caches

frees pagecache, dentries and inodes. Ok.

So, if I want the system to start caching normally again, do I need to reset it to 0 first? My system has the value currently set to 0, which I assume is the default. Or will it reset on its own? I see at least two possibilities here, and I'm not sure which one is true:

  1. echo 3 > /proc/sys/vm/drop_caches frees pagecache, dentries and inodes. The system then immediately starts caching again. I'm not sure what I would expect the value in /proc/sys/vm/drop_caches to do if this is the case. Go back to 0 almost immediately?

  2. If /proc/sys/vm/drop_caches is set to 3, the system does not do any memory caching till it is reset to 0.

Which case is true?

  • 38
    To use it with sudo: echo 3 | sudo tee /proc/sys/vm/drop_caches Commented Aug 3, 2014 at 22:40
  • 1
    Holy cow! @VolkerSiegel I've been scrubbing the Interwebs for hours and randomly found your comment. Tried it and it worked perfectly! Thanks for adding this little trick. I don't want to hijack this question but if it's not inappropriate, I'd like to ask for explanation. When I use sshpass with sudo -i && echo 3 > /proc/sys/vm/drop_caches, I get an error: stdin: is not a tty. Using your "sudo" method works. Why? Commented Feb 26, 2016 at 15:57
  • 3
    @harperville Ask a question; this is almost certainly an unrelated issue. Commented Feb 26, 2016 at 16:36
  • 1
    @harperville Yes - that is a very good question - with an interesting answer, Do ask it separately! Then let me know here. Or you want me to ask the question myself and then answer it? Commented Feb 26, 2016 at 16:57
  • I know this is ages old but for posterity: @harperville I suspect you're actually piping the ssh command to /proc/sys/vm/drop_caches on your local system, which means you'll (if successful, no idea how it behaves with arbitrary input) drop caches on the host you're SSHing from, if at all. Inputting sudo password over SSH is a bit more involved, but doable.
    – Legogris
    Commented Nov 13, 2020 at 15:44

2 Answers 2


It isn't sticky - you just write to the file to make it drop the caches and then it immediately starts caching again.

Basically when you write to that file you aren't really changing a setting, you are issuing a command to the kernel. The kernel acts on that command (by dropping the caches) then carries on as before.

  • 5
    Ok, thanks. Does the value immediately change back to 0? Commented Aug 3, 2011 at 8:49
  • 52
    @FaheemMitha No, the value you can read is whatever you put last, but it's not used anywhere, only the action of writing matters. The source code is in fs/drop_caches.c. Commented Aug 4, 2011 at 0:16
  • Is there a specific benefit for the JVM by doing this? Commented Dec 21, 2016 at 21:31
  • 4
    There are no benefits for applications, on the contrary: files will load slower because no cached inodes. Also, you are not low on memory: if an app needs memory it will take it from the OS cache. See linuxatemyram.com.
    – dr0i
    Commented Jun 12, 2018 at 9:47
  • 2
    No. The sync command flushes dirty buffers to disk so that they can be freed by writing to /proc/sys/vm/drop_caches. This is the writing: echo 3 | sudo tee /proc/sys/vm/drop_caches
    – DylanYoung
    Commented Apr 7, 2020 at 20:48

It is not sticky as said in above. You can use below command as well to clean (along with "sync" as mentioned in the manual):

sudo sh -c "sync; echo 3 > /proc/sys/vm/drop_caches"

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .