All about optimization

[Tomi1231 (Chilly28)]

The real optimization comes from looking at the micro profiler.

What is good to know is the balance between easy to maintain and readable code versus optimized code.
Deprecated functions aren’t often way slower than newer alternatives

[bytesleuth]

@0786ideal

loop need more performance to do

The reply from Roblox staff that I quoted says it doesn’t.

@0786ideal

It ignores the wait because it is an event, it runs everything the condition for the event to happen it met, in the case of heartbeat, physics have been calculated and so it runs the event, and once another event happens, it’ll run that code separately, unlike a while loop which respects waits,

You need to debounce the event to make it work like a while loop, respecting waits and what not

I don’t know what a DF is and what that even means.

[HugeCoolboy2007 (omega)]

@pankii_kust

Humanoids are not the reason game lags, it’s the DEVELOPER that codes it all and those listed in there are also not the reason to blame.

It’s both. Too many Humanoids are harmful for game performance since it has to manage a lot of different characters at the same time, but the developer’s own coding and implementations also play a huge factor as well

[0786ideal (ideal)]

some functions are better to use, for example findPartOnRay vs Workspace:Raycast, or task.wait() vs wait(), or maybe object like body movers - they are good but sometimes they goes badly

[Tomi1231 (Chilly28)]

Yeah, they are nicer to use, but not necessarily faster. task.wait() is better because it can yeild for 1 frame minimum while wait() only yeilds for 2 frames minimum, can’t yeild for only 1 frame. For FindPartOnRay versus WorldRoot:Raycast, I do not know their performance, but I do know that in the case of the (almost deprecated) GetTouchingParts versus WorldRoot:GetPartsInPart, the newer alternative isn’t really faster

Discussion from Introducing OverlapParams - New Spatial Query API:

@kleptonaut

@Pokemoncraft5290

Is there any performance difference between GetPartsInPart and GetTouchingParts ?

Should be pretty much the same performance wise. GetPartsInPart can just simplify things as you do not need to worry about the collision properties of the Part.

WorldRoot uses more optimized collision detection, however, it hasn’t been benchmarked against Region3. So how much faster? idk

For body movers, from what I remember (couldn’t find my sources), BodyMovers run at 240Hz regardless of the Adaptive Timestepping, which will reduce performance if you have a lot of them
The usefulness of the new AlignPosition and AlignOrientation objects can be argued…

[lnconcinnity]

You can only have the HumanoidRootPart and the Humanoid in the server while the client will handle the rendering part of all bodyparts and animations

Hypothetically speaking, you can have 500 or more humanoids with proper implementation, such as unrendering the bodyparts after the humanoid is 500 studs away from the camera and stopping animations after the humanoid is 250 studs away from the camera

[PepeElToro41]

Adding performance settings is great, even if roblox already adds that. This can make people be able to play your game at full graphics, for example, in my old pc I was able to play at max settings, but my pc hated the Depth Of Field effect and wasnt able to hit 60FPS, so having a setting to disable it would be good to be able to play it max graphics without compromising the other visuals

[VSCPlays]

well, you didn’t read this part anyways

@Egzekiel

In the in-game menu, players can choose what type of graphics they want, lowest graphics already disables/simplifies many things.

[x86_architecture (TritiumAndDeuterium)]

@0786ideal

4. Stop using some materials if you don’t need too!
Glass and Neon need more calculations to do. They have reflectance or glowing effects, soo they are heavier than regular plastic or sand.

I’m not really sure if this is still true or not, but I heard somewhere on the devforum, a long time ago, that neon was actually one of the fastest materials on roblox. Supposedly, it’s because roblox doesn’t perform specular / defuse calculations on it or something like that, but I don’t really remember.

[0786ideal (ideal)]

oh, maybe they changed that, it used to be laggy, maybe they fixed that, if yes, take this as outdated point