clearAllMemoizedCaches — Clear all MemoizedFunction caches in the current runtime thread.
clearAllMemoizedCaches removes cached entries and resets counters for every MemoizedFunction registered in the current runtime thread.
Syntax
clearAllMemoizedCaches
status = clearAllMemoizedCachesReturns
status- Type
NumericScalar- Description
- Zero when the operation completes.
Errors
RunMat:memoize:GcFailure- When
- The memoized object target cannot be allocated or accessed.
- Message
memoize: internal object storage failed
RunMat:clearAllMemoizedCaches:TooManyOutputs- When
- More outputs are requested than this form supports.
- Message
clearAllMemoizedCaches: too many output arguments
Behavior
Clears all memoized-function caches known to the runtime.
Preserves the MemoizedFunction objects and their properties.
The operation returns zero internally and suppresses automatic output in statement form.
Execution and placement
Host-side cache bookkeeping only.
Execution limits
Cache bookkeeping uses the current runtime thread. Constructing or inspecting a wrapper does not invoke the wrapped function. Calling the wrapper uses normal callable execution, including that function’s effects, requested outputs, residency, errors and cancellation.
Cache and snapshot allocation is not yet fully owned for finite Managed execution; this API is not evidence of finite cache-memory support.
Example
Clear every memoized cache
clearAllMemoizedCaches;
f = memoize(@sin);
g = memoize(@cos);
f(1); g(1);
clearAllMemoizedCachesExpected output:
% Both caches are empty.Using clearAllMemoizedCaches with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how clearAllMemoizedCaches changes the result.
Run a small clearAllMemoizedCaches example, explain the result, then change one input and compare the output.
FAQ
Does this remove MemoizedFunction objects?⌄
No. Existing objects remain valid; only their cache entries and counters are reset.
Related Introspection functions
addlistener · addParameter · addprop · assignin · builtin · cancel · class · clear · clearCache · clearvars · dbclear · dbstack · dbstatus · dbtype · eval · evalc · evalin · feval · findprop · func2str · functions · get.p · getcallinfo · getmethod · inputname · inputParser · isa · ischar · isdeployed · iskeyword · ismethod · isobject · isstring · isUnderlyingType · isvalid · keyboard · loadobj · localfunctions · matlab.metadata.DynamicProperty.delete · memoize · metaclass · mfilename · mislocked · mlock · munlock · namelengthmax · narginchk · nargoutchk · new_object · notify · numArgumentsFromSubscript · onCleanup · parse · saveobj · set.p · stats · str2func · subsasgn · subsref · superclasses · underlyingType · verLessThan · version · which · who · whos
Source you can read
Every RunMat function's source is public. Read exactly how clearAllMemoizedCaches is executed, line by line, in Rust.
- View the source for clearAllMemoizedCaches in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.