Another thing I'm curious about is whether the loading issue is reproducible on your end if you clear your viewer cache and visit the same location. If you're able to reproduce the slow loading of textures and meshes, the viewer's Texture Console (which I mentioned in your other recent report at https://feedback.secondlife.com/server-bugs/p/mesh-refuses-to-rez-for-lengthy-periods ) should have some interesting stats about mesh and texture download status.

Maestro Linden Log files sent. Thanks for the help Maestro.

Maestro Linden Re your second request: I cleared cache, teleprorted to exactly the same sim location, and the textures for the sim loaded within 60 seconds. I stayed there for a couple of minutes, teleported out, waited 10 seconds, then teleported back in. Textures rezzed instantly. So they were obviously still in my graphics memory. Note on stats: 9 avatars on sim, and it's 7pm as compared to 3:30. Will mention again the extremely slow texture loading was experienced by everyone in our group, without exception. That's 19 people. (We were gathered there by the memorial having a nice chat.) So that rules out my system or my system cache per se, though I'm not denying the system cache may not be working properly. A broken cache would definitely define as a bottleneck. This could be one major bottleneck, or several adding up to a perfect storm. Ten minutes for everything to rez of course is excessive. This evening after clearing cache it worked much better... but it was technically a "different environment" via time of day, number of avatars, and no guessing what other influence or issues going on behind the scenes. There obviously is something that caused 19 people to not rez the sim for ten or more minutes. (Some were already there before I arrived.) Thanks again for checking in to these things. I will stress that this was not an individual experience. Everyone there experienced this to a person... and it happened across multiple regions.

Eren Padar: Thanks for the email, but the attached logs appear to be outdated, from 2024-2025.

For Firestorm logs, it will be in a similar path to the SL logs, but replacing "SecondLife" with "Firestorm". On a Windows machine with default settings, I believe would be the appropriate folder to open in Explorer for logs if you were using Firestorm for that session.

You'll want to check that the modified time of the log file (or UTC timestamps in the lines) corresponds to the right viewer session, as the log file is overwritten each time the viewer is launched.

To reiterate, I also think it would be a good idea to open the Texture Console when experiencing slow performance loading textures or meshes. Texture console is can be accessed via Debug -> Consoles -> Texture Console or Ctrl+Shift+3, and shows the progress of asset loading. There's a lot of information in the console, which is documented at https://wiki.secondlife.com/wiki/Texture_Console

Here's an example run of a viewer with no cache loading a texture-heaving scene with the console open: https://youtu.be/zvxp1lBXO1Y

The quality on YouTube is unfortunately pretty poor until about 40 seconds in, but after that point you can see all the text on the console as it loads the textures.

I think it would be interesting to see what this console shows when you experience poor loading, particularly the values of the 'State' column if there's stalling behavior. For example, it might get stuck on if there's a disk i/o bottleneck due to HDD/filesystem/antivirus performance issues. The State values will also tell you if the viewer is fetching the textures over HTTP or if it's getting them over the old and much-much-slower UDP pipeline for some reason.

Maestro Linden I can't tell for a certainty, but it appears Firestorm dumps old log files daily. (Perhaps that's in my settings, unsure.) Whatever, I could not pull up a log file except for my most recent one. This logically could only be done if I experienced the same thing again, immediately logged out and sent you the log file.

With all respect, let me be honest here: I joined SL in 2004 when I was 49 years old. You can do the math: I'm literally too old for this stuff. What I say is that there were 19 people in that group, and everything was gray for all of them. Beyond that, I avoid deep-dive bug hunting these days. It is both mentally and physically tiring.

Again with respect, if my lack of deep-dive bug hunting means SL continues to not rez properly for multiple people, it's your company. Linden Lab has to decide how this decades-old problem pans out. I mean no disrespect at all; I'm just laying my cards on the table. I truly wish I could help you, but my deep-dive mind isn't as sharp as it used to be. I can still identify bottleneck symptoms, but I'm long-retired from the computer field and glad of it. I'll have to leave Linden Lab bug hunting to Linden Lab. ; )

Maestro Linden What I will do is show you a much smaller "for instance". Today a friend sent me a texture, a photo. I opened it, and what I saw on my screen is attached. That gray screen remained gray for a full minute before the texture rezzed. I have no idea why... but the manifestation was real, it was timed, and I've had friends report to me the exact same thing happens to them. Perhaps this isn't of much help, but it does illustrate the issue. I had been in this room for a good ten or fifteen minutes. I was sitting in place. No new textures were rezzing, nothing changed... yet a photo from my inventory took a full minute to rez. Now we can imagine multiplying that situation by hundreds or thousands of textures. I've already sent my computer specs; my computer is no slouch. I have plenty of RAM. I've used SL for over two decades. This is what I got when a friend sent me a photo: