Firestorm texture entries sl cache viewer

#Firestorm texture entries sl cache viewer install
#Firestorm texture entries sl cache viewer upgrade

I see only minor changes and I consider those within the margin of error for my measuring as these are *NOT rigorously controlled tests. My conclusion is this viewer runs about the same as Firestorm has for the last couple of years. Without days of repeated measurements on both versions over a number of days, I consider it a pretty meaningless number. So, while it is an interesting number at best it can only hint at what is going on. BUTвЂ¦ I canвЂ™t control the complexity of the avatars in the scene. The decrease in NelsoniaвЂ™s w/avatars number is significantly lower. The rest of the numbers are similar to the previous version. I was curious as that wasnвЂ™t mentioned in the thread. It obviously takes more power to render Bellisseria. I did my tests at my old home in Fishergate and my new one in Coyote to provide a comparison on location. I changed to my вЂnewвЂ™ front porch earlier this year when I moved into Bellisseria. Nelsonia Safe Hub 128m DD w/15 Avatars вЂ“ 31В± FPS Old site of Green Room 128m DD вЂ“ 102 вЂ“ 109 FPS Ground-level on my new porch 128m DD вЂ“ 24.1 вЂ“ 24.6 FPS How about, does it seem faster in overall use? That is what I went for with my front porch measurements. Getting precise measurements and eliminating the effects of regions, network, CPU, GPU differencesвЂ¦ to focus on a single thing is tedious. My four cores are all carrying about the same load but the overall use is about 50%, which is similar to past versions. There are 20 to 30+ Firestorm threads running at anyone time. So, detecting a slowing or a speed-up due to the new multiple threads is tricky. That is what I experienceвЂ¦ sometimesвЂ¦ There are some oddities happening when one teleports. I guessed that I might even see FPS dip while textures were decompressed as more CPU cycles would be getting used by the texture processes. I wouldnвЂ™t expect a higher FPS (Frames per Second) rate.

#Firestorm texture entries sl cache viewer upgrade

Beta testers for Firestorm will have had the upgrade for some time.ДЇrom the changes the FS Team has made, I would expect this viewer to be faster at rendering a scene. I think this is the first release of Firestorm that has this upgrade. I think this should only affect your first-time post-install-visits to places you frequent.ДЄ while ago the Firestorm Viewer was upgraded to use the simplified cache developed by the Lab.

#Firestorm texture entries sl cache viewer install

One thing that can affect our perception is this install clears our viewerвЂ™s cache of downloaded content. Neither is precise and measurements are highly influenced by our location in the region, which way we are looking, our cache вЂ“ when did we last visit, the regionвЂ™s construction, and avatar occupancy. A few of us may now and then even time it. I suspect most of us hit a region and consider how long it takes for the place to render. But actually, measuring it well is quite complicated. The major effect of texture decompression is in scene render time. But since it has had little effect on Frames per Second numbers it doesnвЂ™t seem to have been a high priority to change. Decompressing is a task that has bottle-necked performance forever. The big thing is FirestormвЂ™s viewer now uses multiple threads for decompressing textures.

My experience is: this version is better. I just want to consider what people are experiencing based on what I can see and measure. IвЂ™m not going to repeat what she has already written.

This version is covered in detail over on InaraвЂ™s blog here: Firestorm 6.4.21. So, I went and ran my tests, which I rate at one half-a-posterior. Which made me curious because that is NOT my impression. The thread Newest Firestorm version вЂ“ lag monster popped up 8/4. The Firestorm Viewer version 6.4.21 had been out for a bit now.