Aishagain commented at 2017-05-14T15:01:19Z

Oops I forgot to attach the logs sorry!
Here they are

Kyle Linden commented at 2017-05-16T17:08:12Z

Hi Aishagain,

Will you please try using the Second Life project viewer Alex Ivy which is our 64bit version of Second Life. While it is in 'project' status there may be some unexpected issues, but I'd like to see if your performance is better in this viewer. Please use your same test sequence to compare and provide the same set of logs for this viewer test too.

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Project_Alex_Ivy/5.1.0.505089

Please press the Info Provided button when you update this issue.

Thanks!

Aishagain commented at 2017-05-16T21:11:36Z

OK Kyle.

64 bit viewer downloaded and installed. Did the test session much as before. My IMMEDIATE impression was that this is MUCH better, both in presentation and in operation. Scenes resolved much more quickly and the cache was created almost instantly. Upon arrival at the teleport hub at Wirtz the scene resolved almost immediately, certainly within 60 seconds. one issue may be that the log folder for the 64 bit appears to be the same as the 32 bit so I hope the logs ARE there! (If they are not , Goodness knows where they are!)

I cannot run a test using the 32 bit RLV here, it simply would not be relevant and besides there is a cache conflict issue that RLV's developers will need to address.

The second FS 64 bit session is attached. The situation is much as it was before, slow scene rezzing upon TP to Wirtz , and I had to toggle shaders to get the scene textures to load.

I hope this is the info you need.

Whirly Fizzle commented at 2017-05-17T05:31:48Z

Heya Aisha,

Just to clarify the behaviour on Firestorm - is Firestorm slower to rez textures for you only when fetching uncached textures or when loading textures from cache?
The latest LL 64bit session you attached logs for had a clean cache so you were fetching all the textures from the CDN that session. The Firestorm session had a dirty cache.
Can you pick a test region (I recommend Lagland or TextureTest2 - both these regions are specially set up to time texture loading times).
Pick one of these regions and use it for all the tests.
Login to the test region with a clean cache on Firestorm with a 512m draw distance (I know that's high but it's just for these test regions) & wait for all the textures to fetch.
There can be a problem with the CDN being "cold" when you visit a region for the first time, so discount how long the textures take to fetch this first session.
Then clear cache again & login to the same region & time how long the textures take to all fetch.
Then relog to the same region again without clearing cache & time how long it takes for the textures to fetch.
Can you give me the times it takes to load the textures when the cache is clean and when you have all textures on the region cached.

If you have enough time, it would be helpful to repeat the same test with the LL 64bit viewer & give the texture load times on both a clean & a dirty cache.

Can you also attach your settings.xml file from C:\Users\USERNAME\AppData\Roaming\Firestorm_x64\user_settings so I can see if there are any settings you have in Firestorm that may be affecting texture load times.

You did mention you had progressive draw distance stepping (PDD) enabled in Firestorm.
Since the interest list changes, this setting can actually cause slower rez times so I recommend you disable PDD on Firestorm.
Preferences -> Firestorm -> Extras -> untick "Enable progressive draw distance stepping".

Thanks :)

Aishagain commented at 2017-05-17T15:27:57Z

Lor you don't ask for much, Whirly! I'll try. No promises.

Aishagain commented at 2017-05-17T16:18:26Z

OK Job done, though not without a couple of glitches. Twice I could not TP to Texturetest 2, once with FS initially and then on relogging with SLV64 after the cache clearance, so whether that spoils the data I don't know.
Time to fully rez all textures was as follows:

1. FS64first TP there (so mature cache) 5 minutes
2. FS64 initial relog after cache clearance) <2 min
3. FS64 relog to same location)<1 min!
4. SLV 64bit TP to Texturetest2 2 c1min
5. SLV 64 bit (marred by being dumped at a safehub)after cache clearance) c1min again
   NB the second and third set done in FS without stepped DD and with 512m DD set
   FS settings .xml also attached. All files are dated 17th May.

Kyle Linden commented at 2017-05-17T21:15:22Z

Hi Aishagain,

Thank you for the updated report. I'm happy to hear the Second Life project viewer Alex Ivy has improved performance, that's exactly what we hope for in a 64bit viewer. Feel free to keep using it and we'll hopefully see it as the main viewer in the not-too-distant future.

Regarding your FireStorm performance issues I'd advise you to contact their support team directly as they have many configuration settings that could be impacting your performance, which I am not familiar with.

Thanks!