De-Threader/ Trigger Limiter question

[RJHollins]

Question for the Gurus ...

Managing 'triggers' throughout a schematic has been something I've tried to stay mindful of.

In the 'toolbox', I have 2 modules ... 'De-threader' and 'Trigger Limiter 25Hz'.

Curious ... I looked inside the 'De-threader' module and noticed that there is a 'Tick 100' clock inside
It is then I looked at this 'Trigger Limiter 25Hz', and sure enough, it had a 'Tick 25' clock

I've been using the Tick 100 De-threader in many parts of my schematic, and never gave it much thought .... until now

I tested both modules in a schematic section, and both of them performed ... so now I wonder ...

Am I wasting resources using the Tick 100 version ?!?

To clarify, I'm not using these 'de-threaders' in any streaming audio section ... I'm mainly dealing with data arrays [strings, numbers, etc].... and I could easily have 50 or 100+ of these throughout a schematic.

What's the potential impact ???

Thanks!

[Tronic]

The reason is that it eventually replaces the old trigger thread with a new one,
if the previous value of the Flip/Flop changes, controlled by an external trig.
This makes it very often triggers generated from external (type the midi) that sometimes do not close the thread,
and continue to run without ending ever.
Is used a trigger 100, to obtain the likely safety of having the updated data,
without relative delay, as the maximum update speed of the greens is 100 Triggers/Seconds.
If this implies a waste of CPU load?
The answer may be no, but also yes, it depends.
Each De-Threder being activated by the trig that arrives,
then for all the time it is inactive.
The Primitive Trigger limit only work, when it is exported.

[RJHollins]

Each De-Threder being activated by the trig that arrives,
then for all the time it is inactive.

Thank-you Tronic ... this helped me to better understand