I am trying to create a tower (you can’t go in it) with glowing windows. However, it is cramping up my workspace and surely could cause some lag.
And this is only a small part of it
Is there any better way to make all these lights? Thanks for any help!
Union all the parts with the same color and material into one.
Okay, yeah, that works but don’t you think that would cause more lag?
How is that going to cause more lag? Personally when I make games that load a lot of parts, I usually union certain parts so less parts are loaded for people.
turning these off for every part should help with the lag a bit, but if you’re looking for the best performance, you should Union all of them and then turn it into a mesh in case it gets deleted by a Union failed loading glitch. and then do the same for the union by turning all of these off again.
It shouldn’t cause much lag because it’ll all load in as one whole part
If you plan on turning that building into a mesh with zero optimisation, you more than likely won’t notice performance differences if you’re only using the asset once because you won’t be reducing its triangle count.
Generally speaking, BaseParts are more optimised than unions and meshes because their geometry is consistent and already known by the client. They take much less time to render. If you don’t plan on spamming the same model an insane number of times there is no point in turning it into a mesh - especially if you don’t plan on optimising it.
Adding everything into a giant union is also bad practice. Not only would you not be reducing the triangle count again, your game would also need to load a much more complex shape which will just result in longer load times. For example, 20 highly efficient BaseParts would load in much faster than if they were instead used in a complex union. (cc @SweetBIackCat @Dewbloxer).
The building itself is probably around 40 parts at a guess (judging from the image), so there’s no need to be concerned about performance anyway. If you consider part count alone, lower-end devices can usually handle a few thousand parts within a reasonable area without seeing any performance issues. You should use the MicroProfiler to properly analyse performance in future and it’s always good practice to follow standard optimisation methods as you work.
If your Workspace is cluttered you should consider grouping pieces of the building or organising models into folders if need be. Just please don’t make unions for the sake of making unions - you should use them when you need to 
