Difference between revisions of "LlGetSPMaxMemory"
Jump to navigation
Jump to search
m (added date of release) |
|||
| Line 34: | Line 34: | ||
|cat3=Script Profiler | |cat3=Script Profiler | ||
|cat4 | |cat4 | ||
|history = Date of Release [[ Release_Notes/Second_Life_Server/11#11.06.17.233176 | 17/06/2011 ]] | |||
}} | }} | ||
Revision as of 12:28, 25 June 2013
| 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 |
Deep Notes
History
Date of Release 17/06/2011
Search JIRA for related Issues
Signature |
|---|
function integer llGetSPMaxMemory(); |