There have been some optimizations made to scheduler in Rivendell 3. I'm not aware of any issues with scheduler codes in the 2.x branch, but the stack that keeps track of carts for artist/title separation grows indefinitely which could severely slow down log generation. Rivendell 3 purges the stack during maintenance runs which helps to keep log generation quick.
Our Rivendell 3 beta system creates 24 hour logs in under a minute. — Patrick patr...@scnv.net > On Mar 19, 2019, at 9:22 AM, Chuck <dj.chuc...@googlemail.com> wrote: > > We're still on v2.10.3, but yes, it takes 4 hours to create one day's > music log of 432 songs using scheduler codes to separate rock and R&B. > We run 2 logs, one music only, the other stopsets and programs with > macros to switch between them. On the other hand, takes only about 2 > minutes to create a day's stopset log which does not use scheduler > codes. > > --Chuck W. > > On Tue, 19 Mar 2019 19:37:44 +0800 > Stan Fotinos <sfoti...@rtrfm.com.au> wrote: > >> Hi all >> >> I have just experimented using scheduler codes to create music >> clocks. What I am finding is that it takes approximately 5 mins to >> create 1 hour with 20 music tracks per hour and approximately 2hrs to >> create to create a day?s music log. >> >> If I only use a group or groups with no codes it takes approximately >> 30 seconds to create an hour clock. >> >> Could some one please tell me if this is the amount it should take to >> create 20 tracks per hour? Anyone else experienced anything similar? >> >> Centos 7 Rivendell 2.19.3 >> >> Thank you >> >> Stan > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
