- #SL CACHE VIEWER WALKTHROUGH FULL#
- #SL CACHE VIEWER WALKTHROUGH FREE#
Every time new data is added to the cache, the VFS looks at the list for a free block which has enough space. The Cache space is then chopped into blocks and managed by a list with a file name like .106525339. The VFS Cache is initialized to the maximum size it allows.
In the /Caches/SecondLife folder confirm there is a file named like .106525339 which will match the VFS Cache size. Confirm that whatever cache size is set, the VFS Cache Size is always 20 % of that value. Search for VFS and confirm the line initCache: VFS CACHE SIZE: 204 MB is present. In the SecondLife/logs folder open the SecondLife.log file. In Preferences>Setup change the cache size to 1024 MB. There may be some additional mesh data received and written to the cache if not viewing exactly the same scene as in previous session. Confirm that the the Show Render console that this mesh data is being read from the cache. Log out and log back in and observe roughly the same Mesh data. Observe and record the values for Mesh Data received and Mesh cache read and write. Log in and fly around a region with several mesh objects. Confirm 0 MB of mesh data is received and 0 Mb written to the cache - the amount read from the cache should be consistent with the size of the mesh minus the 4 kb header. Important to take this into account when confirming expected values in the Show Render display. Note: Because the first 4 kb of a mesh is fetched and cached when getting the header, if the whole mesh is under 4 kbytes subsequent loads just pull from the cache (or if some LOD of the mesh fits in the first 4 KB) and no additional data is written to the cache for that mesh. This would confirm (according to the values displayed in the console) that the mesh cache was being used to retrieve the mesh object. 
Confirm that MB Mesh cache read is the equivalent of the size of the mesh minus ~4 kb - the first 4 kb are fetched and cached previously when getting the header. Rez the same object again and confirm that no change is seen in the MB Mesh data received also no change should be seen in the MB written to the cache.Confirm that that amount was also written to the cache in the Read/Write section.
After login, view the rezed mesh and observe the change in MB Mesh data received - that is the size of the mesh in MB. In Preferences > Setup select the Reset button next to Cache location to clear the cache (requires relog). Import a mesh that is is larger than 4 kb (duck.dae will work) and rez the object in-world to an area where there are no other objects that will be added or removed during the test. Confirm the mesh cache should indicate 0 / 0 Mb read/write (or close to it) Log into area where you are not viewing or near any meshes. The Mesh Cache data can be viewed in Develop > Show Info > Show Render. #SL CACHE VIEWER WALKTHROUGH FULL#
Also that expected behavior is occurring when the Mesh Cache is empty and full and any performance differences when viewing cached data.Ĭonfirm Mesh Cache Tests Using Show Render Display The purpose of this test is to confirm that Mesh data is being cached where expected and when objects are in the cache those objects are retrieved from the cache and not re-requested.
0 kommentar(er)
