Difference between revisions of "Viewer Memory Manager"
Jump to navigation
Jump to search
Steve Linden (talk | contribs) (New page: = Summary = Currently the Second Life Viewer uses default memory allocators on OSX and Linux, and SmartHeap on Windows. None of these solutions provide run time memory profiling. When last...) |
Rand Linden (talk | contribs) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Archive}} | |||
= Summary = | = Summary = | ||
Currently the Second Life Viewer uses default memory allocators on OSX and Linux, and SmartHeap on Windows. None of these solutions provide run time memory profiling. When last investigated, Windows saw approximately a 15% overall framerate improvement when using SmartHeap. We need to find a cross platform solution that preserves as much of this performance optimization as possible while providing hooks for run time memory profiling. | Currently the Second Life Viewer uses default memory allocators on OSX and Linux, and SmartHeap on Windows. None of these solutions provide run time memory profiling. When last investigated, Windows saw approximately a 15% overall framerate improvement when using SmartHeap. We need to find a cross platform solution that preserves as much of this performance optimization as possible while providing hooks for run time memory profiling. | ||
= Objectives = | = Objectives = | ||
* Replace SmartHeap on Windows with a memory allocation library that is cross-platform and open source | * Replace SmartHeap on Windows with a memory allocation library that is cross-platform and open source | ||
** It needs to | ** It needs to allow us to track memory allocations at run time. This could be a command line option if there is a performance overhead, but the overhead needs to be low enough to continue to run real time. | ||
** Performance must remain comparable to SmartHeap on Windows | ** Performance must remain comparable to SmartHeap on Windows | ||
** The ability to dump a detailed memory profile would enable residents to | ** The ability to dump a detailed memory profile would enable residents to submit memory leak / bloat information to Linden Lab and the OS community | ||
= See Also = | |||
* [[Viewer Roadmap]] | |||
Latest revision as of 10:42, 5 May 2011
 |
This article is obsolete, but kept as a historical record. Do not rely on this information in any way. However, it may be used in the future, so please do not delete or modify. |
Summary
Currently the Second Life Viewer uses default memory allocators on OSX and Linux, and SmartHeap on Windows. None of these solutions provide run time memory profiling. When last investigated, Windows saw approximately a 15% overall framerate improvement when using SmartHeap. We need to find a cross platform solution that preserves as much of this performance optimization as possible while providing hooks for run time memory profiling.
Objectives
- Replace SmartHeap on Windows with a memory allocation library that is cross-platform and open source
- It needs to allow us to track memory allocations at run time. This could be a command line option if there is a performance overhead, but the overhead needs to be low enough to continue to run real time.
- Performance must remain comparable to SmartHeap on Windows
- The ability to dump a detailed memory profile would enable residents to submit memory leak / bloat information to Linden Lab and the OS community