This is what happens when the most bloated frameworks in existence are forced into things they do not need to be in. Not everything needs to be a web dev pattern. Someone told the gui framework to “update” the leaderboard every once in a while without thinking about how that update will be done. The obscure spaghetti code implementation decided that it should destroy and recreate ALL gui instances associated with the player list every “update”. 13 ms is roughly 650 instances being destroyed and re created. Even when the list is “disabled”, this is probably as naively done as merely parenting to nil without disabling the update code, so the core scripts are still destroying and creating instances that aren’t even rendered.
3 Likes
I appreciate the reply and confirmation that the performance issues of in-experience UI components is been investigating and worked on by multiple engineers.
Though, I’ve expected and hoped for a much faster resolution to this issue especially since as you’ve said that it is top concern for the teams that work on this and that they’re trying to resolve it as soon as they can. These issues has been reported since a long while and it’s a pity that they still haven’t been fixed yet and that we aren’t getting constant updates about them that would at least give us the impression that they’re actually being worked on and not ignored or forgotten.
I just hope that this all can be resolved quickly and that I wouldn’t see the React Scheduler or ExperienceChatMain or PlayerListManager or any of the Corescripts taking up huge frame times and tanking frame rates anymore.
These issues shouldn’t have happened and shouldn’t happen again if they get resolved, why would UI components with poor performance be released out to the public, has there been no testing to them or was it thought that it was just a good idea releasing them with that state?
To be more specific, who even thought it was a good idea using React/Roact everywhere on UIs on Roblox even though this framework is known for having poor performance and optimization, this is besides that Roblox got their very own optimization and implementation issues that makes this even worse. This is just unnecessary. We don’t need web stuff everywhere, we don’t need React/Roact on Roblox, pretty sure their cost overweights their outcomes. Roblox was fine without it, and I am pretty sure anything you can make through them can be made natively using Luau.
6 Likes
Hey @ItzAidfoplays390 thank you very much for sharing your feedback on this. We recognize the negative sentiment these performance issues are causing and the impact its having on creators on the platform 
We are treating this matter with urgency and are putting a plan together to provide more frequent updates on our progress towards resolving these issues.
Thanks again!
5 Likes
Just one small thing that I want to note is that, I hope and would expect for actual or bigger improvements and results with every update.
While the recent updates under the announcement post of “Improvements to Experience Chat”, did improve the performance of the in-experience chat to a certain extent, it wasn’t a lot or that much noticeable. It kind of just reduced the effect of spikes with 3ms less or so.
Also, while there is a huge noticeable improvement on how much resources are consumed by ExperienceChatMain when the chat is disabled through either player settings or when the default chat UI is disabled, I’ve noticed that while the amount of resources consumed are very little, the chat still does that when it is completely disabled through player settings, I would expect it to not do at all.
Hope this concern related to ExperienceChatMain would get addressed and the same for all CoreScripts that currently suffer performance issues in the first point.
I’ve noticed in the announcement post that more promising improvements and fixes with bigger impact are in the pipe and coming out soon, so I hope these will make a bigger difference with the performance of ExperienceChatMain.
That’s all, and thank you again for everything!
4 Likes