llGetUsedMemory

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

GetUsedMemory

llGetUsedMemory

Summary

Function: integer llGetUsedMemory( );

0.0	Forced Delay
10.0	Energy

Returns the integer of the number of bytes of memory currently in use by the script.

Specification

This function's behavior is dependent upon the VM the script is using. Mono is the new VM, LSO is the old VM. The big difference between Mono and LSO is that Mono scripts run faster and can utilize four times more memory.

Mono

In Mono the value returned is the amount of memory currently in use by the script. This is achieved by searching the script's stack and counting all reachable resources. In terms of garbage collection, memory that hasn't been GC'd doesn't count against the script's memory limit when it's no longer reachable.^[1]

The reason why Mono/SLua implements its memory limits this way is because there's a single VM/GC governing their scripts, and you don't want to "stop the world" to run the garbage collector just to see if you can get a single script back under its limit.

LSO

LSO scripts always use 16KiB of memory.

Caveats

• Scripts compiled to LSO always report 16KB memory used.
• This can be called at any time and does not require llScriptProfiler

Examples

Calling llGetUsedMemory can look like this:

integer used_memory = llGetUsedMemory();
llOwnerSay((string)used_memory + " bytes of memory currently used.");

Notes

The amount of used memory is updated only at the start of a server frame, meaning the values from this function can fluctuate. To ensure stable values, it's possible to wait until the next frame, e.g. llSleep(0.01) before the call to llGetUsedMemory.

See Also

Functions

•	llGetFreeMemory
•	llSetMemoryLimit
•	llScriptProfiler

Deep Notes

History

Date of Release 17/06/2011

Footnotes

1. ^ Explanation given by Harold Linden in the official Discord server.

Signature
function integer llGetUsedMemory();