Difference between revisions of "Plugin architecture Stability"
Jump to navigation
Jump to search
Iron Perth (talk | contribs) |
Iron Perth (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Methods for | == Plugin Performance and Stability Issues == | ||
The following is a discusson on some of the performance and stability risks that plugins will create and ways to deal with them. | |||
'''Stability and Performance Risks''' | |||
* Plugins consuming too much cpu time, entering into spin locks | |||
* Plugin memory leaks | |||
'''Methods for handling Client Stability and Performance''' | |||
* Master switch to turn off all plugins. | * Master switch to turn off all plugins. | ||
This could be useful when Linden Lab is providing support for a problem, or someone is having issues with their client. | This could be useful when Linden Lab is providing support for a problem, or someone is having issues with their client. | ||
* Startup / Safe mode with no plugins running | |||
* Reporting stack traces for seg faulting software to plugin developers | |||
Latest revision as of 20:01, 12 February 2007
Plugin Performance and Stability Issues
The following is a discusson on some of the performance and stability risks that plugins will create and ways to deal with them.
Stability and Performance Risks
- Plugins consuming too much cpu time, entering into spin locks
- Plugin memory leaks
Methods for handling Client Stability and Performance
- Master switch to turn off all plugins.
This could be useful when Linden Lab is providing support for a problem, or someone is having issues with their client.
- Startup / Safe mode with no plugins running
- Reporting stack traces for seg faulting software to plugin developers