Will this cause lag?

[HaaG]

Will having like 5-10 triggers at once running at 0.02 sec each cause some lag? Even minor?

 

[Nichilus]

depends on what the trigger does.
Also afaik there is no need to have a trigger run faster than .03 second

 

[WereElf]

I have a similar question.
I have 4 triggers that are runing every 0,1 seconds. Can they cause lag, or shall I set them to run every 0,15 seconds?

 

[Name_n]

What exactly are you looping

are you checking for a certain condition?

 

[kingkwong]

Every 0.01 seconds
Do nothing

This won't lag.

It depends what you are doing. If you have a lot of actions being carried out then yes it will lag. Most triggers don't need to be that fast and you can usually find a way to fix it. Make sure you clear all your leaks because if you leak that many times per second then you will defiantly lag.

 

[WereElf]

The triggers themselves aren't leaking.
What they are doing:
pick a random point from the playable map area, and drop a meteorite there. Wait 2,4 seconds (until the meteorite falls), and they pick all the player controlled units in range, and damage them.

 

[kingkwong]

The triggers themselves aren't leaking.
What they are doing:
pick a random point from the playable map area, and drop a meteorite there. Wait 2,4 seconds (until the meteorite falls), and they pick all the player controlled units in range, and damage them.

Thats not really going to lag. What are you doing every 0.1 seconds anyway?
Only really small values such as 0.01 is going to cause extreme lag with heaps of actions. I don't understand why you guys are asking rather than just using it. If it lags then post the triggers here and people can help optimize it.

 

[Acutesharpness]

Those kind of events will have insane amount of server stress (network) which lag THROUGH the network spam, having more than ONE of those 0.02 triggers is and will make the game Glitchy due to the game inability to process it (only applies in multiplayer) And makers often ask why the fuck does my spell lag and guess wut, create 1 thousand units.

 

[SAUS]

The triggers themselves aren't leaking.
What they are doing:
pick a random point from the playable map area, and drop a meteorite there. Wait 2,4 seconds (until the meteorite falls), and they pick all the player controlled units in range, and damage them.

Creating a wait 10 times per second can cause problems when you play online. It will create input delay for everyone if there are too many or if some other latency is happening it can make it worse to have a bunch of waits (even if they normally don't cause anything noticeable).

Every 0.1 seconds is not a problem at all, though. I would just update these to use timers. It is a really big boost to accuracy and map speed, and it's a very standard practice in JASS code (which you are learning about from what I've seen).

 

[WereElf]

Creating a wait 10 times per second can cause problems when you play online. It will create input delay for everyone if there are too many or if some other latency is happening it can make it worse to have a bunch of waits (even if they normally don't cause anything noticeable).

Every 0.1 seconds is not a problem at all, though. I would just update these to use timers. It is a really big boost to accuracy and map speed, and it's a very standard practice in JASS code (which you are learning about from what I've seen).

Yeah, I am planing to rewrite my triggers in JASS when I get the time.
I did these triggers when I still had no idea how to do them with timers.
Anyways... 0,1 seconds isn't a problem, even if it runs 4 times at once? (The 4 triggers essentially do the same thing. I just turn off/on some of them, depending on the game difficulty chosen)

 

[SAUS]

Yeah, I am planing to rewrite my triggers in JASS when I get the time.
I did these triggers when I still had no idea how to do them with timers.
Anyways... 0,1 seconds isn't a problem, even if it runs 4 times at once? (The 4 triggers essentially do the same thing. I just turn off/on some of them, depending on the game difficulty chosen)

It shouldn't be a problem if that's all they're doing. It will only be a problem over network (and even then, you may not notice it until there is some latency from a player outside things from inside the game or you add a bunch of other waits for a spell or something).

It's probably better to have them condensed into one trigger (perhaps even just timers with no triggers once you go full JASS), but it shouldn't be a problem. You'd notice it, most likely, if it were a problem. Just note that adding many things like this will eventually cause problems. It's just when it starts hitting the threshold of being too much that it becomes an obvious, big problem.