Difference between revisions of "LlGetSPMaxMemory"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
(Created page with "{{LSL_Function |func_id=???|func_sleep=0.0|func_energy=??? |func=LlGetSPMaxMemory |return_type=integer |func_desc |Return_text=of the most bytes used while LlScriptProfiler w…") |
|||
| Line 15: | Line 15: | ||
=== LSO === | === LSO === | ||
This function has no effect for scripts not compiled to Mono. | This function has no effect for scripts not compiled to Mono. It will always return 16384, the fixed LSO memory size. | ||
|caveats= | |caveats= | ||
*The number of free bytes the Heap can use may be greater but not less. | *The number of free bytes the Heap can use may be greater but not less. | ||
Revision as of 17:25, 17 April 2011
| 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 at any one time.
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.
Examples
See Also
Functions
| • | llGetFreeMemory | |||
| • | llGetUsedMemory |