Difference between revisions of "Streaming Cost test"
Jump to navigation
Jump to search
Dan Linden (talk | contribs) (Created page with "Category:Test Plans Category:Mesh '''Test Plan Name:'''<br /> : Streaming Cost test '''Sources''' : none == Purpose == Verify the amount of data streamed to the viewer i…") |
Dan Linden (talk | contribs) |
||
| Line 4: | Line 4: | ||
: Streaming Cost test | : Streaming Cost test | ||
'''Sources''' | '''Sources''' | ||
: | : https://wiki.secondlife.com/wiki/Mesh_Accounting_Test | ||
== Purpose == | == Purpose == | ||
Revision as of 14:41, 12 January 2011
Test Plan Name:
- Streaming Cost test
Sources
Purpose
Verify the amount of data streamed to the viewer is within the expected range.
Tests
Target viewport streaming cost at 128m, medium detail (currently 2MB)
- "I got this number by flying around some prim heavy builds (the city north of Ahern) with all rendering disabled but prims, view distance set to 128m, and prim detail set to mid, and watching the peak triangle count per frame in the statistic floater. The average was around 75k/triangles per frame with a peak of 150k, so for meshes a good target would be 125k. On MeshHQ 3, after disabling all rendering but prims (meshes fall under the same category as prims in the render pipeline), the peak triangle count per frame was close to 300k/triangles. On that build, there was no LoD enforcement and a ratio of 8KB/prim for mesh costs, so I'm hoping with a ratio of 4KB/prim and strict LoD enforcement, recreating that build within the new criteria will result in under 125k/triangles per frame."