Hi Fred
Thank you for the clarification, so all the improvements should be
already implemented in the version I am testing with 2.19.3. As Cliff
suggested I did try a modern PC with a very fast processor and lots of
RAM, it did reduce the time taken by 50 minutes ( it previously took 2
hours for 24 hrs of music) It still appears to be a long time
considering the low complexity of the set up...
Thanks
Stan
On 21/03/2019 4:07 am, Fred Gleason wrote:
On Tue, 2019-03-19 at 10:00 -0700, Lorne Tyndale wrote:
Yes, as I recall there were some optimizations that were initially
tested in V2, but then made their way into V3. From what I
understand
the changes make use of temporary MySQL tables when creating the log
instead of doing things in arrays.
The optimizations were part of the final batch of improvements
submitted by Alban Peigner before Tryphon ceased operations. They first
appeared in v2.12.0, and improved music scheduler performance when
generating logs by an order of magnitude or more. Thus, an update to
the current stable version (v2.19.3) should cure the OP's reported
bottleneck.
Cheers!
|---------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|---------------------------------------------------------------------|
| A room without books is like a body without a soul. |
| |
| -- Cicero |
|---------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
