Asset manager loads longer with Large models

The asset manager seems to take longer to load existing inventories when switching between groups. In this video I attempt to upload a model containing 47,000 descendants, and then another with 10,000. The one with 47k instances took ~10 sec to get where I needed. The 10k barely took 2 seconds.

https://cdn.discordapp.com/attachments/816184919445209148/1134351774858350672/Screen_Recording_2023-07-27_at_9.57.14_PM.mov

Expected behavior
Asset manager should load group inventories at the same speed regardless of the size of the model.

5 Likes

Hey @Usering, thanks for bringing this to our attention! We’re looking into it now and will get back to you with more details.

1 Like

Hello again Usering, I helped you last time on Large models cause asset configuration window to slow down.

So I’m a bit confused, is this related to this other bit you mentioned on that thread? You mentioned you thought it was the same bug, so maybe there was something I missed

The window runs much faster now with our larger model, the fix there is much appreciated. However I constantly run into the issue of the wrong user/group being loaded; this happens if you select a different owner while results are loading for your own user models. If that race condition could be patched my model publishing experience would be much improved.

Did the fix we released for your other bug report fix another issue, but not this one, or did this regress?

1 Like

The previous bug was about both frame performance/responsiveness of asset manager due to the preview viewport (which has been addressed) as well as the amount of time asset manager takes to load my inventory (which this specific bug is referencing and is still a problem). From what I can observe it looks like the size of the model impacts how fast asset manager can load.

1 Like

Okay, so even though the asset is not being previewed, it still takes a substantial amount of time to load. Do I have that right? And it seems to fix itself after the first time it loads?

Yes. Once the inventory does load, swapping between group inventories is instant. This happens the same way every time I open asset manager to re-publish the same models. I can DM one of the models I’m uploading

1 Like

Okay, I found the issue. The model you gave me has a bunch of sounds in it, and it’s waiting to confirm you have access to every single sound before showing you everything else. Confirm this with yourself by trying to publish a version that doesn’t have any sounds :slight_smile:

Working on a fix, thank you!

2 Likes

Very interesting, most of those sounds don’t need to be there anyways. The model I filmed the original post with does contain all of our actual game sounds. Thanks for looking into this!

1 Like

Hey do you know when this will be patched? There are occasions it never loads my inventory, in this screenshot I started a publish, made myself lunch and came back to the window still loading.

It looks like the fix I wrote for this isn’t working very well so I might need to give it some more attention…

Hey have there been any updates here? Asset manager is still incredibly sluggish

I unfortunately haven’t had the time to look into this…

Like mentioned by you earlier in the post months ago, looking through my studio logs and some testing today I was able to find out it’s because of how many sound instances there are within the thing being published.

When publishing a model with a ton of those my studio is sending a HTTP request for each one, for example here’s a few of the requests of the 523 it sent for my model I experience the issue on:


Roblox Server IPs in that don’t worry.

When I removed all the audios and for sake of it replaced with other random assets like parts the delay was gone.

Here’s a repro file its just a folder with 500 audio instances each with a different audio ID. Simply select the folder and see the delay when uploading to an existing user/group model.
Audio Instances Delay Asset Manager Repro.rbxm (4.0 KB)
You can also have 500 of the same sound ID and it will still send a HTTP request for each instance. Even sends requests for those legacy/app file audios.