LlGetSPMaxMemory

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/fr 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

GetSPMaxMemory

LlGetSPMaxMemory

Summary

Function: integer LlGetSPMaxMemory( );

???	Function ID
0.0	Forced Delay
???	Energy

Returns the integer of the most bytes used while LlScriptProfiler was last active.

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 between Mono and LSO is that Mono scripts run faster and can utilize four times more memory.

Mono

During and after a LlScriptProfiler profiling run, llGetSPMaxMemory will return the most memory used during profiling.

LSO

This function has no effect for scripts not compiled to Mono. It will always return 16384, the fixed LSO memory size.

Caveats

• The number of free bytes the Heap can use may be greater but not less.

All Issues ~ Search JIRA for related Bugs

Examples

See Also

Functions

•	llGetFreeMemory
•	llGetUsedMemory

Deep Notes

Search JIRA for related Issues

Signature
function integer LlGetSPMaxMemory();