MEMORY-PURGE(3valkey)
π memory-purge β the "please give the RAM back" button π
okay so hi bestie π«Ά you're reading the Valkey Command Manual page for memory-purge, which lives in manual section 3valkey. yes the command name is memory-purge even though the actual thing you type is two whole words, we'll get to that, stay with me β¨
πΈ NAME πΈ
memory-purge β literally just asks the allocator to release memory. that's it. that's the whole job. π
π SYNOPSIS π
MEMORY PURGE
no args, no flags, no drama. it's giving minimalism π
π¦ DESCRIPTION π¦
so here's the tea β the MEMORY PURGE command attempts to purge dirty pages, so that the allocator can reclaim them. it's basically the equivalent of telling your room "hey. clean yourself." and hoping it listens π
and now the part you actually need to know: this command is currently implemented only when you're usingjemallocas the allocator. for every other allocator it evaluates to a benignNOOPβ meaning it does absolutely nothing, but politely, and it won't yell at you or error out. lowkey the chillest no-op in the whole codebase π
β¨ REPLY β¨
valkey-protocol(7) simple string reply: OK.
that's it. OK. no payload, no extra data, just vibes π
π COMPLEXITY π
depends on how much memory is allocated, and it could be slow.
yeah. not "might be" slow. could be slow. if your instance is holding onto a whole lot of memory, this is not a "run it mid-request and forget about it" situation, bestie π plan accordingly.
π ACL CATEGORIES π
@slow
she is literally filed under slow. the category tag said it first, don't come for me π
π§ HISTORY π§
- available since:
4.0.0
an icon that's been around since 4.0.0, we stan a legacy queen π
π SEE ALSO π
like a group chat of related commands, all of them in (3valkey):
acl(3valkey)acl-cat(3valkey)acl-deluser(3valkey)acl-dryrun(3valkey)acl-genpass(3valkey)acl-getuser(3valkey)acl-help(3valkey)acl-list(3valkey)acl-load(3valkey)acl-log(3valkey)acl-save(3valkey)acl-setuser(3valkey)acl-users(3valkey)acl-whoami(3valkey)bgrewriteaof(3valkey)bgsave(3valkey)command(3valkey)command-count(3valkey)command-docs(3valkey)command-getkeys(3valkey)command-getkeysandflags(3valkey)command-help(3valkey)command-info(3valkey)command-list(3valkey)commandlog(3valkey)commandlog-get(3valkey)commandlog-help(3valkey)commandlog-len(3valkey)commandlog-reset(3valkey)config(3valkey)config-get(3valkey)config-help(3valkey)config-resetstat(3valkey)config-rewrite(3valkey)config-set(3valkey)dbsize(3valkey)debug(3valkey)failover(3valkey)flushall(3valkey)flushdb(3valkey)info(3valkey)lastsave(3valkey)latency(3valkey)latency-doctor(3valkey)latency-graph(3valkey)latency-help(3valkey)latency-histogram(3valkey)latency-history(3valkey)latency-latest(3valkey)latency-reset(3valkey)lolwut(3valkey)memory(3valkey)memory-doctor(3valkey)memory-help(3valkey)memory-malloc-stats(3valkey)memory-stats(3valkey)memory-usage(3valkey)module(3valkey)module-help(3valkey)module-list(3valkey)module-load(3valkey)module-loadex(3valkey)module-unload(3valkey)monitor(3valkey)psync(3valkey)replconf(3valkey)replicaof(3valkey)restore-asking(3valkey)role(3valkey)save(3valkey)shutdown(3valkey)slowlog(3valkey)slowlog-get(3valkey)slowlog-help(3valkey)slowlog-len(3valkey)slowlog-reset(3valkey)swapdb(3valkey)sync(3valkey)time(3valkey)
tl;dr bestie: typeMEMORY PURGE, getOK, maybe reclaim some dirty pages if you're onjemalloc, and get literally nothing if you're not. no cap. π«Ά
and that's the whole page!! this one came to you from version 9.0.0, dated 2025-10-21, in MEMORY-PURGE(3valkey) β tysm for reading, mwah πβ¨
π¦ where this page comes from
- fedora 44: valkey-doc 9.0.3-2.fc44 Β· CC-BY-SA-4.0
- fedora 44: valkey-doc 9.0.6-1.fc44 Β· CC-BY-SA-4.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms