Are spawn functions laggy?

Help and Feedback Scripting Support
#1

Hello everyone , not much to ask here. Are spawn functions laggy? Lets say in every script I have 2 spawn functions to allow code to run simultaneously, is this laggy? do I have to break the spawn? (all I have in spawns usually are wait() )

1 Like
#2

spawn is really bad to use, instead use coroutine

#3

It is not laggy at all. I am pretty sure.

#4

what makes spawn so bad to use?

#5

Spawn isnt bad, I do not see how coroutines spawn someone better.

#6

It is not bad and not laggy, spawns is good for your games!

#7

Spawns are more outdated, there are a lot of topics about how bad it is to use spawn or delay

1 Like
#8

isnt their a yeild before a spawn function?

#9

Hm, really? How comes mine work perfectly fine

#10

spawn() gives a delay to your function, I suggest you completely AVOID using spawn() and use this instead

coroutine.resume(coroutine.create(function()
    -- do something
end))
1 Like
#11

is coroutine just as easy to use as spawn, also that means i have to replace all my scripts with spawn with coroutine oof

#12

oh? and that provides the same result as running code simultaneously? that’s easier than i thought thank you!

#13

Please mark rokoblox5 has the solution if he helped you.

1 Like
#14

Since spawn() has a built-in wait() a lot could go wrong in the process, I personally use coroutines as they have no built-in delays.

In general, you should avoid Debris:AddItem(), spawn() and other functions that has a delay added to them.

#15

Debris does not yield the current thread, does not require a new thread and will not error if the object is already destroyed. For this reason it is the recommended method for cleaning up objects with a fixed lifetime.

local debris = game:GetService("Debris")
local averageTime = 0

for i = 1, 10 do
    wait(10)
    local parts = {}
    for i = 1, 250 do
	    table.insert(parts, Instance.new("Part", game.Workspace))
    end

    local startTime = os.clock()
    for _, part in pairs(parts) do
	    debris:AddItem(part, 5)
    end
    local endTime = os.clock()

    averageTime += (endTime - startTime)
    print(endTime - startTime)
end

print(averageTime / 10)

The average time upon running the Debris part of this function was 0.15ms, with the max being 0.18ms. Debris does not yield the thread.

#16

Debris is :Destroy() with a delay, it is the same, except for the built-in delay Debris has.
And, I never said that Debris yields the current thread, because it doesn’t.

Here’s why I use :Destroy() over :AddItem().

#17

task.spawn() doesn’t give a delay any longer to the function, u still think coroutines are better?

1 Like
#18

This is an old post dude. I believe this was before they added a task library, 2 years ago btw.

1 Like