I often use ServerStorage on asset creating places to store a bunch of assets out of the way in a place where Studio doesn’t immediately have to load them whenever I open the place. This works out great, and has for years. However, for about 2 months now, moving assets (models/parts) to ServerStorage has suddenly become a major headache.
Whenever I move bulk items (about 50 or more models) into ServerStorage, Studio grinds to a stop. This is to be expected a little bit, as moving assets into storage has always taken some computing power. However, the way it happens now is unacceptable. I have sat staring at my screen for over an hour on multiple occasions waiting for the operation to complete. Almost every time, I get fed up and use TaskManager to force close Studio. On very few occasions, I have let Studio do its thing and gotten things done around the house. When doing this, I have seen it take upwards of 3-5 hours to complete the operation. So, it’s happening, but at a horrid pace. I have since been forced to stop using ServerStorage for this purpose on construction maps (not even places people are meant to play!) because I cannot justify waiting this amount of time.
The problem continues to ReplicatedStorage. I have a custom chunk loading system for scenery (trees, scenery buildings, etc.) because my maps are usually huge and the built in Streaming system breaks everything I’m doing (that’s a story for another day). The custom chunk loader replicates assets near the client from ReplicatedStorage. This system has worked flawlessly for me and helps performance big time. However, just as it is with moving assets into ServerStorage, when I want to pull the foliage out of ReplicatedStorage because there’s a pesky tree in the middle of a road I have to delete, I literally cannot get the folder of assets to move back into ReplicatedStorage. Studio again freezes, and just sits there. Once, it was a very bad problem and I just had to get some foliage straightened out. So, I moved everything out of ReplicatedStorage (taking things out is still pretty quick, it’s only returning them that sucks) and made my changes. It was about bedtime, so I set the parent of my asset folder to where it belongs in ReplicatedStorage and went to bed. I woke up in the morning, it was still frozen. I left it and went to work. When I got home from work, it had completed the operation, after taking 18-20 hours to do so.
I have an older PC, running a 1050TI graphics card and other similar era hardware. However, most of Roblox functions great for what I do. What got me is that this issue came out of nowhere. It was fine (a few minutes at most) one day, and terrible the next (takes hours).
To replicate the issue:
Have a bulk number of assets (around 50-100 models, usually vehicles or buildings for me).
I keep those assets inside a Folder.
Parent the Folder containing the assets to ServerStorage (or ReplicatedStorage).
Go make dinner, do laundry, take a nap, grab a coffee, and watch your favorite movie while you wait.
Another form of bulk assets for me would be several thousand low-poly single-part trees (mesh parts) inside a Folder, being moved into ReplicatedStorage.
