Difference between revisions of "LlGetSPMaxMemory"
Jump to navigation
Jump to search
m |
|||
| Line 23: | Line 23: | ||
{{LSL DefineRow||[[llGetFreeMemory]]|}} | {{LSL DefineRow||[[llGetFreeMemory]]|}} | ||
{{LSL DefineRow||[[llGetUsedMemory]]|}} | {{LSL DefineRow||[[llGetUsedMemory]]|}} | ||
{{LSL DefineRow||[[llGetMemoryLimit]]|}} | |||
{{LSL DefineRow||[[llSetMemoryLimit]]|}} | |||
|also_events | |also_events | ||
|also_tests | |also_tests | ||
Revision as of 13:01, 11 December 2012
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
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
Examples
See Also
Functions
| • | llGetFreeMemory | |||
| • | llGetUsedMemory | |||
| • | llGetMemoryLimit | |||
| • | llSetMemoryLimit |