Practical limit for concurrent running timelines?

fogled@mizzou

Is there a practical limit? I'm looking at running 25 timelines all the time, and adding another up to 50 temporary timlines as needed. I haven't seen any obvious problems in my tests yet, but I still have a long way to go on this program.

gusgizmo

I'm kind of curious as well about the overhead of timelines. I wonder at what point is it better to combine multiple timelines together, because the overhead of running the timeline is greater than the load created by the code inside the timeline.

Would it be possible to refactor your code so that you have a lower number of timelines running? Maybe don't do so yet (premature optimization and all that), but perhaps keep it in mind as you create your code.

In any case, from my experience, timelines are well optimized in AMX, and most likely you won't have any issues. I would ensure that I was running the latest firmware on my master however, it seemed that much older firmwares had issues with timeline execution.

Danny Campbell

I have a single program with 30 timelines defined. Only 15 will ever be running at one time. This on a NI-2100. No problems at all.

It is a system that runs 15 touch panels that are on the outside wall of 15 different conference rooms. They are the RMS welcome panels, and the timelines run a slideshow on each panel. Baiscally, when the montion sensor detects someone nearby, it will disable the slideshow and start a countdown that is reset each time the sensor fires or someone touches the panel. After one minute of being left alone the first timeline expires and starts the slideshow timeline.

Danny

fogled@mizzou

gusgizmo wrote: »

Would it be possible to refactor your code so that you have a lower number of timelines running?

Yes, I definitely have an option to replace a set of 25 separate timelines with a single timeline, and will do that if I see any real bog-downs in my current setup.