Difference between revisions of "Improving Region Performance"

From Second Life Wiki
Jump to: navigation, search
m (1 revision)
(Revised Parature import)
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{Seal}}
 
{{Seal}}
 
 
  
 
This article explains how to check your Second Life region's performance and some steps you can take to improve it. This article has been written with owners of Estates (sometimes referred to as islands) in mind, but mainland owners may find parts of it helpful.
 
This article explains how to check your Second Life region's performance and some steps you can take to improve it. This article has been written with owners of Estates (sometimes referred to as islands) in mind, but mainland owners may find parts of it helpful.
 
  
 
==Checking Your Region's Performance==
 
==Checking Your Region's Performance==
 
  
 
To see the performance of your region you'll want to check the region's Frames Per Second (FPS). To do this you can use the [[Statistics Bar Guide|Statistics Bar]]. While standing on your land, select '''View > Statistics Bar'''. This can be a bit overwhelming, so we'll guide you through the relevant parts here.
 
To see the performance of your region you'll want to check the region's Frames Per Second (FPS). To do this you can use the [[Statistics Bar Guide|Statistics Bar]]. While standing on your land, select '''View > Statistics Bar'''. This can be a bit overwhelming, so we'll guide you through the relevant parts here.
 
  
 
[[Image:kb_region_fps.png]]
 
[[Image:kb_region_fps.png]]
 
  
 
''Statistics Bar with '''Sim FPS''' (a measure of your region's Frames Per Second) highlighted.''
 
''Statistics Bar with '''Sim FPS''' (a measure of your region's Frames Per Second) highlighted.''
  
 
+
{{KBnote| '''Note: Sim''' stands for "simulator" and, for the purposes of this article, is another name for "region."
{{KBnote| '''Sim''' stands for "simulator" and, for the purposes of this article, is another name for "region."
+
 
}}
 
}}
 
  
 
To interpret the '''Sim FPS''' performance of your region:
 
To interpret the '''Sim FPS''' performance of your region:
 
  
 
* 45 FPS: The highest possible value. No action necessary.
 
* 45 FPS: The highest possible value. No action necessary.
Line 29: Line 20:
 
* 10 - 35 FPS: This is slow, and should be noticeable. Adjustment is needed to improve your region's performance.
 
* 10 - 35 FPS: This is slow, and should be noticeable. Adjustment is needed to improve your region's performance.
 
* 0 - 10 FPS: This is pretty much terrible. You may have trouble moving or performing simple tasks. See above.
 
* 0 - 10 FPS: This is pretty much terrible. You may have trouble moving or performing simple tasks. See above.
 
  
 
If your performance of your region is consistently over 35 FPS at its busiest time, you can stop reading here. Fortunately, most regions are above 35 FPS most of the time. For example, during the month of October 2007, all the Second Life regions were below 35 FPS an average of less than 2% of the time.
 
If your performance of your region is consistently over 35 FPS at its busiest time, you can stop reading here. Fortunately, most regions are above 35 FPS most of the time. For example, during the month of October 2007, all the Second Life regions were below 35 FPS an average of less than 2% of the time.
 
  
 
In the screenshot above, you'll notice the '''Sim FPS''' is '''21''', which means the region is very slow. The '''Main Agents''' line shows '''96''', which is the number of agents (avatars) currently in your region. This is exceptionally high, and is likely the prime cause of this region's slow FPS. The '''Child Agents''' line displays the number of avatars outside your region that can see into it, which can also slow your region down if it's a significant number.
 
In the screenshot above, you'll notice the '''Sim FPS''' is '''21''', which means the region is very slow. The '''Main Agents''' line shows '''96''', which is the number of agents (avatars) currently in your region. This is exceptionally high, and is likely the prime cause of this region's slow FPS. The '''Child Agents''' line displays the number of avatars outside your region that can see into it, which can also slow your region down if it's a significant number.
 
  
 
To see more detail on what's slowing down your region, expand the [[Statistics Bar Guide|Statistics Bar]] by clicking on the '''Time (ms)''' line; additional region statistics will appear:
 
To see more detail on what's slowing down your region, expand the [[Statistics Bar Guide|Statistics Bar]] by clicking on the '''Time (ms)''' line; additional region statistics will appear:
 
  
 
[[Image:kb_stats_time.png]]
 
[[Image:kb_stats_time.png]]
 
  
 
The '''Total Frame Time''' displays the number of milliseconds needed (ms) to display a single frame. '''Total Frame Time''' greater than '''22.2 ms''' means your '''Sim FPS''' will be below '''45 FPS'''. For a detailed explanation of the values beneath '''Total Frame Time''', see the [[Statistics Bar Guide|Statistics Bar article]]'s Time section. However, we'll explain some of these measurements below as we walk through the ways to improve your region's performance.
 
The '''Total Frame Time''' displays the number of milliseconds needed (ms) to display a single frame. '''Total Frame Time''' greater than '''22.2 ms''' means your '''Sim FPS''' will be below '''45 FPS'''. For a detailed explanation of the values beneath '''Total Frame Time''', see the [[Statistics Bar Guide|Statistics Bar article]]'s Time section. However, we'll explain some of these measurements below as we walk through the ways to improve your region's performance.
  
 
==Improving Your Region's Performance==
 
==Improving Your Region's Performance==
 
  
 
There are a number of steps that you can take to improve your region's performance. We've listed the steps in approximate order of the biggest impact and least effort. It's worth noting, however, that each region is unique.
 
There are a number of steps that you can take to improve your region's performance. We've listed the steps in approximate order of the biggest impact and least effort. It's worth noting, however, that each region is unique.
 
  
 
===Reduce the Maximum Number of Avatars in Your Estate===
 
===Reduce the Maximum Number of Avatars in Your Estate===
 
  
 
The number of avatars in a region is the most common cause and usually the biggest contributor to low region FPS. This number has often been increased above the default setting of 40, resulting in lower region performance. Lowering the number of avatars in your region can usually increase your region's FPS. This can be done in the '''Region''' tab of the Region/Estate window ('''World > Region/Estate'''); adjust the '''Agent Limit''' field to specify the number of avatars allowed in your region at any one time.
 
The number of avatars in a region is the most common cause and usually the biggest contributor to low region FPS. This number has often been increased above the default setting of 40, resulting in lower region performance. Lowering the number of avatars in your region can usually increase your region's FPS. This can be done in the '''Region''' tab of the Region/Estate window ('''World > Region/Estate'''); adjust the '''Agent Limit''' field to specify the number of avatars allowed in your region at any one time.
 
  
 
[[Image:kb_agent_limit.png]]
 
[[Image:kb_agent_limit.png]]
 
  
 
The default '''Agent Limit''' setting is '''40'''. As an estate owner, you can adjust this setting. We recommend looking at the '''Agent Time''' in the [[Statistics Bar Guide|Statistics Bar]] to see how well your region is performing during your busiest time. Keeping your '''Agent Time''' below '''9ms''' during its busiest time is a good idea.
 
The default '''Agent Limit''' setting is '''40'''. As an estate owner, you can adjust this setting. We recommend looking at the '''Agent Time''' in the [[Statistics Bar Guide|Statistics Bar]] to see how well your region is performing during your busiest time. Keeping your '''Agent Time''' below '''9ms''' during its busiest time is a good idea.
 
  
 
===Remove Top Scripts===
 
===Remove Top Scripts===
 
  
 
Inefficient or very busy scripts in your region can slow it down. In the [[Statistics Bar Guide|Statistics Bar]], the '''Script Time''' line shows how many milliseconds each of the scripts in your region is taking to run. If this value is over 5 milliseconds, then it may be worth checking to see if it can be reduced. To see which scripts are the busiest in your region, open the '''Debug''' tab in your Region/Estate window and click '''Get Top Scripts''', which will open the Top Scripts window.
 
Inefficient or very busy scripts in your region can slow it down. In the [[Statistics Bar Guide|Statistics Bar]], the '''Script Time''' line shows how many milliseconds each of the scripts in your region is taking to run. If this value is over 5 milliseconds, then it may be worth checking to see if it can be reduced. To see which scripts are the busiest in your region, open the '''Debug''' tab in your Region/Estate window and click '''Get Top Scripts''', which will open the Top Scripts window.
 
  
 
[[Image:kb_top_scripts.png]]
 
[[Image:kb_top_scripts.png]]
 
  
 
* Clicking twice on the '''Time''' column heading sorts the busiest scripts at the top.
 
* Clicking twice on the '''Time''' column heading sorts the busiest scripts at the top.
 
* Since this list is based on a small slice of time, it's a good idea to click '''Refresh''' a few times to get a more accurate picture.
 
* Since this list is based on a small slice of time, it's a good idea to click '''Refresh''' a few times to get a more accurate picture.
 
* Selecting a line and clicking '''Show Beacon''' activates a beacon inworld highlighting the object running the selected script.
 
* Selecting a line and clicking '''Show Beacon''' activates a beacon inworld highlighting the object running the selected script.
 
  
 
Once you know which scripts are consuming your region's resources, you can remove, replace or optimize them. Also, note that reducing the total number of scripts in your region can improve performance.
 
Once you know which scripts are consuming your region's resources, you can remove, replace or optimize them. Also, note that reducing the total number of scripts in your region can improve performance.
 
  
 
Examples of problematic scripts include:
 
Examples of problematic scripts include:
 
  
 
* Scripts that are constantly active without sleeping; for example: Sensor scripts with less than a few-second sleep interval.
 
* Scripts that are constantly active without sleeping; for example: Sensor scripts with less than a few-second sleep interval.
 
* Temp-rezzer scripts that allow a slightly larger number of prims at the expense of region performance.
 
* Temp-rezzer scripts that allow a slightly larger number of prims at the expense of region performance.
 
  
 
===Remove Top Colliders===
 
===Remove Top Colliders===
 
  
 
Physical objects can potentially slow your region down. Specifically, physical objects that are often moving and collide with each other can contribute significantly to the time your region takes to perform the physics calculations. In the [[Statistics Bar Guide|Statistics Bar]], the '''Sim Time (Physics)''' line shows how many milliseconds your physics calculations are taking. If this value is over '''4''' milliseconds, then it may be worth check to see if this can be reduced. To see which colliders are the most active, open the '''Debug''' tab in your Region/Estate window and click '''Get Top Colliders''', which will open the Top Colliders window.
 
Physical objects can potentially slow your region down. Specifically, physical objects that are often moving and collide with each other can contribute significantly to the time your region takes to perform the physics calculations. In the [[Statistics Bar Guide|Statistics Bar]], the '''Sim Time (Physics)''' line shows how many milliseconds your physics calculations are taking. If this value is over '''4''' milliseconds, then it may be worth check to see if this can be reduced. To see which colliders are the most active, open the '''Debug''' tab in your Region/Estate window and click '''Get Top Colliders''', which will open the Top Colliders window.
 
  
 
* Clicking twice on the '''Time''' column heading sorts the most active colliders at the top.
 
* Clicking twice on the '''Time''' column heading sorts the most active colliders at the top.
 
* Since the top colliders list is based on a small time slice, it's a good idea to click '''Refresh''' a few times to get a more accurate picture.
 
* Since the top colliders list is based on a small time slice, it's a good idea to click '''Refresh''' a few times to get a more accurate picture.
 
* Selecting a line and clicking '''Show Beacon''' will activate a beacon inworld highlighting the selected object.
 
* Selecting a line and clicking '''Show Beacon''' will activate a beacon inworld highlighting the selected object.
 
  
 
Once you know which objects are your top colliders, you can remove, replace or optimize them. Also note that lowering the total number of moving objects in your region can improve performance.
 
Once you know which objects are your top colliders, you can remove, replace or optimize them. Also note that lowering the total number of moving objects in your region can improve performance.
 
  
 
===Remove Large Textures===
 
===Remove Large Textures===
 
  
 
Excessive use of large textures can slow down a region. In general, it's a good idea to avoid using textures greater than 512x512 pixels. In the [[Statistics Bar Guide|Statistics Bar]], the '''Images Time''' line tells you how many milliseconds the handling of your region's images is taking. If this value is over 2 milliseconds, it may be worth checking to see if it can be reduced: When a person's avatar views a large image or numerous smaller images for the first time since entering the region, they'll automatically download the image to their Second Life viewer. If a number of avatars are doing this simultaneously, a significant load is created on your region, slowing down its FPS. If you can't remove these large textures, the following strategies might be useful for increasing your region's performance:
 
Excessive use of large textures can slow down a region. In general, it's a good idea to avoid using textures greater than 512x512 pixels. In the [[Statistics Bar Guide|Statistics Bar]], the '''Images Time''' line tells you how many milliseconds the handling of your region's images is taking. If this value is over 2 milliseconds, it may be worth checking to see if it can be reduced: When a person's avatar views a large image or numerous smaller images for the first time since entering the region, they'll automatically download the image to their Second Life viewer. If a number of avatars are doing this simultaneously, a significant load is created on your region, slowing down its FPS. If you can't remove these large textures, the following strategies might be useful for increasing your region's performance:
 
  
 
* Reducing the number of unique textures
 
* Reducing the number of unique textures
 
* Reducing the size of textures
 
* Reducing the size of textures
 
* Reducing the resolution of textures
 
* Reducing the resolution of textures
 
  
 
===Optimize Scripted Texture-Changing Objects===
 
===Optimize Scripted Texture-Changing Objects===
 
  
 
Scripted objects that change textures can also slow down a region. Each time a new texture is displayed, it must be downloaded to each avatar looking at the object. If you can't remove these objects, then reducing the number and size of unique textures in these objects can increase your region's performance.
 
Scripted objects that change textures can also slow down a region. Each time a new texture is displayed, it must be downloaded to each avatar looking at the object. If you can't remove these objects, then reducing the number and size of unique textures in these objects can increase your region's performance.
 
  
 
===Reduce the Number of Prims Used===
 
===Reduce the Number of Prims Used===
 
  
 
Reducing the number of prims your region uses will increase your region's performance. Regions are currently limited to 15,000 prims, but if you stay significantly below this number, your region performs noticeably better.
 
Reducing the number of prims your region uses will increase your region's performance. Regions are currently limited to 15,000 prims, but if you stay significantly below this number, your region performs noticeably better.
 
  
 
===Reduce Number of Objects===
 
===Reduce Number of Objects===
 
  
 
Large numbers of objects will slow your region down, especially if they're of any of the following types:
 
Large numbers of objects will slow your region down, especially if they're of any of the following types:
 
  
 
* Moving
 
* Moving
Line 134: Line 94:
 
* Scripted
 
* Scripted
 
* Shape-changing sculpties
 
* Shape-changing sculpties
 
  
 
===Reduce Visitor Attachments===
 
===Reduce Visitor Attachments===
 
  
 
While this is harder to do, some regions have seen improvement by having visitors remove attachments, especially high-prim or heavily scripted ones.
 
While this is harder to do, some regions have seen improvement by having visitors remove attachments, especially high-prim or heavily scripted ones.
 
  
 
===Region Optimizations for Improved Viewer Performance===
 
===Region Optimizations for Improved Viewer Performance===
 
  
 
The following region items can slow down viewer performance:
 
The following region items can slow down viewer performance:
 
  
 
* Big prims greater than 10 m x 10 m can slow down viewer FPS. These kind of objects cannot be created under normal circumstances.
 
* Big prims greater than 10 m x 10 m can slow down viewer FPS. These kind of objects cannot be created under normal circumstances.
 
* Large or numerous textures, when an avatar first comes within sight of them
 
* Large or numerous textures, when an avatar first comes within sight of them
* Overuse of sculpted prims, twisted tori, and other geometrically complex objects.
+
* Overuse of [https://wiki.secondlife.com/wiki/Sculpted_Prims sculpted prims], twisted tori, and other geometrically complex objects.
 
* Particle effects (which includes bling and poofers).
 
* Particle effects (which includes bling and poofers).
 
  
 
Keep in mind some of your visitors may have slow graphics cards or PCs. [[Typical Frame Rate Performance by Graphics Card/GPU|This article]] discusses frame rate performance per graphics processing unit (GPU).
 
Keep in mind some of your visitors may have slow graphics cards or PCs. [[Typical Frame Rate Performance by Graphics Card/GPU|This article]] discusses frame rate performance per graphics processing unit (GPU).
 
  
 
===More Info on the Region/Estate Window ===
 
===More Info on the Region/Estate Window ===
 
  
 
You can perform numerous other estate management tasks using the [[The Region/Estate window|Region/Estate Window]].
 
You can perform numerous other estate management tasks using the [[The Region/Estate window|Region/Estate Window]].
 
  
 
==A Frequently-Asked Question About Frames Per Second==
 
==A Frequently-Asked Question About Frames Per Second==
 
  
 
"You know, I have a videogame that runs at a framerate much, much higher than Second Life's. Why is that?"
 
"You know, I have a videogame that runs at a framerate much, much higher than Second Life's. Why is that?"
 
  
 
The quick answer: ''User-generated content.''
 
The quick answer: ''User-generated content.''
 
  
 
The reason why your videogame has such a luxurious, silken-smooth framerate is because its content is pre-rendered, and either installs to your hard drive before you've even begun playing, or streams to your computer from your CD or DVD-ROM drive faster than a contemporary internet connection could hope to be.
 
The reason why your videogame has such a luxurious, silken-smooth framerate is because its content is pre-rendered, and either installs to your hard drive before you've even begun playing, or streams to your computer from your CD or DVD-ROM drive faster than a contemporary internet connection could hope to be.
 
  
 
Content in Second Life isn't pre-rendered. It's created on the fly and updated constantly by countless individual users every second of every day while being fed to your computer through the internet. All of these factors make Second Life a much more dynamic, complicated world to render, which results in a framerate that's nominally lower than a top-of-the-line first-person shooter. This isn't to say Second Life's maximum framerate might not improve later -- the future is ever unknowable -- but those of you wondering why your region doesn't compare to your favorite next-generation shooter now have your answer.
 
Content in Second Life isn't pre-rendered. It's created on the fly and updated constantly by countless individual users every second of every day while being fed to your computer through the internet. All of these factors make Second Life a much more dynamic, complicated world to render, which results in a framerate that's nominally lower than a top-of-the-line first-person shooter. This isn't to say Second Life's maximum framerate might not improve later -- the future is ever unknowable -- but those of you wondering why your region doesn't compare to your favorite next-generation shooter now have your answer.
 
  
 
==Conclusion==
 
==Conclusion==
 
  
 
Despite the fact that on average, regions are only below 35 FPS a small percentage of the time, we understand that slow region performance can be aggravating (to say the least). For those region and estate owners, we've described how to achieve good performance by monitoring the [[Statistics Bar Guide|Statistics Bar]] during your busiest times and using the Region/Estate window's tools to adjust the number of avatars, scripts, textures, objects and moving physical objects in your region. We hope this article helps you find the right balance between making your region impressive and fast.
 
Despite the fact that on average, regions are only below 35 FPS a small percentage of the time, we understand that slow region performance can be aggravating (to say the least). For those region and estate owners, we've described how to achieve good performance by monitoring the [[Statistics Bar Guide|Statistics Bar]] during your busiest times and using the Region/Estate window's tools to adjust the number of avatars, scripts, textures, objects and moving physical objects in your region. We hope this article helps you find the right balance between making your region impressive and fast.

Revision as of 17:00, 31 December 1969

Kb-seal.png

This article is part of the Extended Second Life Knowledge Base that includes advanced and specialized information. This information was originally provided by Linden Lab, but is not actively maintained nor guaranteed to be accurate. Linden Lab does not certify nor assume any responsibility for this information.

See the official Second Life Knowledge Base for the most current information.

This article explains how to check your Second Life region's performance and some steps you can take to improve it. This article has been written with owners of Estates (sometimes referred to as islands) in mind, but mainland owners may find parts of it helpful.

Checking Your Region's Performance

To see the performance of your region you'll want to check the region's Frames Per Second (FPS). To do this you can use the Statistics Bar. While standing on your land, select View > Statistics Bar. This can be a bit overwhelming, so we'll guide you through the relevant parts here.

Kb region fps.png

Statistics Bar with Sim FPS (a measure of your region's Frames Per Second) highlighted.

KBnote.png Note: Note: Sim stands for "simulator" and, for the purposes of this article, is another name for "region."

To interpret the Sim FPS performance of your region:

  • 45 FPS: The highest possible value. No action necessary.
  • 35 - 44 FPS: This is quite good; you don't need to tune if it never goes below 35 FPS.
  • 10 - 35 FPS: This is slow, and should be noticeable. Adjustment is needed to improve your region's performance.
  • 0 - 10 FPS: This is pretty much terrible. You may have trouble moving or performing simple tasks. See above.

If your performance of your region is consistently over 35 FPS at its busiest time, you can stop reading here. Fortunately, most regions are above 35 FPS most of the time. For example, during the month of October 2007, all the Second Life regions were below 35 FPS an average of less than 2% of the time.

In the screenshot above, you'll notice the Sim FPS is 21, which means the region is very slow. The Main Agents line shows 96, which is the number of agents (avatars) currently in your region. This is exceptionally high, and is likely the prime cause of this region's slow FPS. The Child Agents line displays the number of avatars outside your region that can see into it, which can also slow your region down if it's a significant number.

To see more detail on what's slowing down your region, expand the Statistics Bar by clicking on the Time (ms) line; additional region statistics will appear:

Kb stats time.png

The Total Frame Time displays the number of milliseconds needed (ms) to display a single frame. Total Frame Time greater than 22.2 ms means your Sim FPS will be below 45 FPS. For a detailed explanation of the values beneath Total Frame Time, see the Statistics Bar article's Time section. However, we'll explain some of these measurements below as we walk through the ways to improve your region's performance.

Improving Your Region's Performance

There are a number of steps that you can take to improve your region's performance. We've listed the steps in approximate order of the biggest impact and least effort. It's worth noting, however, that each region is unique.

Reduce the Maximum Number of Avatars in Your Estate

The number of avatars in a region is the most common cause and usually the biggest contributor to low region FPS. This number has often been increased above the default setting of 40, resulting in lower region performance. Lowering the number of avatars in your region can usually increase your region's FPS. This can be done in the Region tab of the Region/Estate window (World > Region/Estate); adjust the Agent Limit field to specify the number of avatars allowed in your region at any one time.

Kb agent limit.png

The default Agent Limit setting is 40. As an estate owner, you can adjust this setting. We recommend looking at the Agent Time in the Statistics Bar to see how well your region is performing during your busiest time. Keeping your Agent Time below 9ms during its busiest time is a good idea.

Remove Top Scripts

Inefficient or very busy scripts in your region can slow it down. In the Statistics Bar, the Script Time line shows how many milliseconds each of the scripts in your region is taking to run. If this value is over 5 milliseconds, then it may be worth checking to see if it can be reduced. To see which scripts are the busiest in your region, open the Debug tab in your Region/Estate window and click Get Top Scripts, which will open the Top Scripts window.

Kb top scripts.png

  • Clicking twice on the Time column heading sorts the busiest scripts at the top.
  • Since this list is based on a small slice of time, it's a good idea to click Refresh a few times to get a more accurate picture.
  • Selecting a line and clicking Show Beacon activates a beacon inworld highlighting the object running the selected script.

Once you know which scripts are consuming your region's resources, you can remove, replace or optimize them. Also, note that reducing the total number of scripts in your region can improve performance.

Examples of problematic scripts include:

  • Scripts that are constantly active without sleeping; for example: Sensor scripts with less than a few-second sleep interval.
  • Temp-rezzer scripts that allow a slightly larger number of prims at the expense of region performance.

Remove Top Colliders

Physical objects can potentially slow your region down. Specifically, physical objects that are often moving and collide with each other can contribute significantly to the time your region takes to perform the physics calculations. In the Statistics Bar, the Sim Time (Physics) line shows how many milliseconds your physics calculations are taking. If this value is over 4 milliseconds, then it may be worth check to see if this can be reduced. To see which colliders are the most active, open the Debug tab in your Region/Estate window and click Get Top Colliders, which will open the Top Colliders window.

  • Clicking twice on the Time column heading sorts the most active colliders at the top.
  • Since the top colliders list is based on a small time slice, it's a good idea to click Refresh a few times to get a more accurate picture.
  • Selecting a line and clicking Show Beacon will activate a beacon inworld highlighting the selected object.

Once you know which objects are your top colliders, you can remove, replace or optimize them. Also note that lowering the total number of moving objects in your region can improve performance.

Remove Large Textures

Excessive use of large textures can slow down a region. In general, it's a good idea to avoid using textures greater than 512x512 pixels. In the Statistics Bar, the Images Time line tells you how many milliseconds the handling of your region's images is taking. If this value is over 2 milliseconds, it may be worth checking to see if it can be reduced: When a person's avatar views a large image or numerous smaller images for the first time since entering the region, they'll automatically download the image to their Second Life viewer. If a number of avatars are doing this simultaneously, a significant load is created on your region, slowing down its FPS. If you can't remove these large textures, the following strategies might be useful for increasing your region's performance:

  • Reducing the number of unique textures
  • Reducing the size of textures
  • Reducing the resolution of textures

Optimize Scripted Texture-Changing Objects

Scripted objects that change textures can also slow down a region. Each time a new texture is displayed, it must be downloaded to each avatar looking at the object. If you can't remove these objects, then reducing the number and size of unique textures in these objects can increase your region's performance.

Reduce the Number of Prims Used

Reducing the number of prims your region uses will increase your region's performance. Regions are currently limited to 15,000 prims, but if you stay significantly below this number, your region performs noticeably better.

Reduce Number of Objects

Large numbers of objects will slow your region down, especially if they're of any of the following types:

  • Moving
  • Rotating
  • Scripted
  • Shape-changing sculpties

Reduce Visitor Attachments

While this is harder to do, some regions have seen improvement by having visitors remove attachments, especially high-prim or heavily scripted ones.

Region Optimizations for Improved Viewer Performance

The following region items can slow down viewer performance:

  • Big prims greater than 10 m x 10 m can slow down viewer FPS. These kind of objects cannot be created under normal circumstances.
  • Large or numerous textures, when an avatar first comes within sight of them
  • Overuse of sculpted prims, twisted tori, and other geometrically complex objects.
  • Particle effects (which includes bling and poofers).

Keep in mind some of your visitors may have slow graphics cards or PCs. This article discusses frame rate performance per graphics processing unit (GPU).

More Info on the Region/Estate Window

You can perform numerous other estate management tasks using the Region/Estate Window.

A Frequently-Asked Question About Frames Per Second

"You know, I have a videogame that runs at a framerate much, much higher than Second Life's. Why is that?"

The quick answer: User-generated content.

The reason why your videogame has such a luxurious, silken-smooth framerate is because its content is pre-rendered, and either installs to your hard drive before you've even begun playing, or streams to your computer from your CD or DVD-ROM drive faster than a contemporary internet connection could hope to be.

Content in Second Life isn't pre-rendered. It's created on the fly and updated constantly by countless individual users every second of every day while being fed to your computer through the internet. All of these factors make Second Life a much more dynamic, complicated world to render, which results in a framerate that's nominally lower than a top-of-the-line first-person shooter. This isn't to say Second Life's maximum framerate might not improve later -- the future is ever unknowable -- but those of you wondering why your region doesn't compare to your favorite next-generation shooter now have your answer.

Conclusion

Despite the fact that on average, regions are only below 35 FPS a small percentage of the time, we understand that slow region performance can be aggravating (to say the least). For those region and estate owners, we've described how to achieve good performance by monitoring the Statistics Bar during your busiest times and using the Region/Estate window's tools to adjust the number of avatars, scripts, textures, objects and moving physical objects in your region. We hope this article helps you find the right balance between making your region impressive and fast.