TEXTURE REZZING DATA-- Firestorm Viewer latest versionsIlan Tochner wrote: ↑Mon Oct 19, 2020 12:21 amHi Snoots,
Do you get different results when you open a texture that has been accessed recently (but isn't in your viewer cache) and one that hasn't been opened recently?
TEST #1:
2020-10-19 7:45-7:50am
LOCATION: Weefolk Township, Wellspring
Rezzing a 1024x512 texture I just uploaded: 17 seconds following end of upload and double-clicking on texture to view.
Rezzing same 1024x512 texture after waiting a few minutes: 17 seconds
(Avatar position had not changed. No other textures were rezzed in interim.)
Prior to test avatar had been at location for quite some time, with all local textures fully loaded.
------------------
TEST #2: OSgrid
Cleared cache. Set Draw Distance to 32m prior to logging in. Logged in to OSgrid on an empty parcel, nothing within 512m.
Rezzed textures directly from inventory, using stopwatch timer.
#1: 1024x512 1.5 seconds
#2: 1024x512 1.5 seconds
#3: 512x512 1 second
#4: 512x512 1.5 seconds
#5: 512x512 1.5 seconds
#6 512x512 1.6 seconds
#7: 512x512 .9 seconds
#8: 512x512 1.4 seconds
Starting over from texture #1:
#1: Instantly
#2: .5 seconds
#3: .7 seconds
#4: 1.2 seconds
#5: 1.4 seconds
#6: 1 second
#7: .9 seconds
#8: 1.5 seconds
------------------
TEST #3: Similar to Test 2 on Kitely.
Cleared cache. Set Draw Distance to 32m prior to logging in. Logged in to Kitely at Wellspring Sandbox. Nothing within 128m.
Rezzed textures directly from inventory, using stopwatch timer.
#1: 1024x512 12 seconds
#2: 256x128 2.2 seconds
#3: 256x256 8 seconds
#4: 512x512 14 seconds
#5: 512x512 11 seconds
#6: 1024x512 14 seconds
#7: 1024x512 5 seconds
#8: 1024x1024 8 seconds
Starting over from texture #1:
#1: 1.5 seconds
#2: Instantly
#3: 4.1 seconds
#4: 4.8 seconds
#5: 1.7 seconds
#6: 11 seconds <---
#7: 2.3 seconds
#8: Instantly <---
------------------
TEST #4: Similar to Tests 2 &3 on Second Life
On a platform 500m in the sky, nothing within 256m
#1: 512x512 1.1 seconds
#2: 1024x512 1.3 seconds
#3: 1024x512 1.4 seconds
#4: 512x512 1.7 seconds
#5: 1024x512 .9 seconds
#6: 1024x512 1.4 seconds
#7: 1024x512 1.4 seconds
#8: 1024x512 1.5 seconds
Starting over from texture #1:
All textures loaded either instantly, in less than a second, or faster than first timing.
Fast enough I had difficulty timing them so gave it up as "qood enough". ; )
Overall impression: What we are seeing on Kitely could be a bottleneck, but takes more the form of "erratic". All figures however showed much slower than OSgrid, which was comparable to SL.
Since SL with its immense asset load performed well within acceptable parameters, this would indicate issues within the Opensim product, Firestorm, or both. However, I was using the SL version of Firestorm on SL, so if it's a Firestorm issue (which from what other users post, it partially is), then it is specific to the Opensim version of Firestorm. But since the same version of Firestorm was used for OSgrid and Kitely, data points to a bottleneck or erratic asset fetching/display in the Kitely system. However...
Taking the analysis one step further: since other posters report no texture load problems using other viewers, this might indicate a compatibility issue between FirestormOS and Kitely. Or it could be a problem with Firestorm that the OSgrid devs have located and fixed... or a problem with Opensim that other Viewer devs are aware of and have fixed. Whatever the problem, it is evident someone somewhere has both identified the problem and come up with a solution... which might be good news. The solution could be as close as a few inquiries to other devs. : )