Increase Playlist Generator Pro Generating Calculation Rapidity

[Altec]

Hi Dmitry,

When you have a big Database, and when you are using tags and priorities options, more you have options much time you spent to generate. It Took approximately 1 hour and 30 minutes to generate 24 hours program.

I don't know if the engine could be optimized, but let me know about it.

Thanks

Altec

 

[djsoft]

When you have a big Database, and when you are using tags and priorities options, more you have options much time you spent to generate. It Took approximately 1 hour and 30 minutes to generate 24 hours program.

I don't know if the engine could be optimized, but let me know about it.

Majority of time is spent loading the categories, so what you can do to speed things up:

• Ensure the music is on a local drive (network drives have latency)
• Local drive is highly recommended to be SSD
• Use SQLite for additional information: https://manual.djsoft.net/radioboss/en/additional-information-storage.htm (it's the default in recent versions, but if you were using RadioBOSS before version 6.0 you could have APEv2 and it's slower).
• Organize the library, if it's really huge (100K+ records), and categories only use a tiny subset of it, you can create smaller libraries to fit the category needs. It's for situations where you filter out 90% of the tracks, it will spend a lot of time reading information for all those tracks.

 

[Altec]

Majority of time is spent loading the categories, so what you can do to speed things up:

• Ensure the music is on a local drive (network drives have latency)
• Local drive is highly recommended to be SSD
• Use SQLite for additional information: https://manual.djsoft.net/radioboss/en/additional-information-storage.htm (it's the default in recent versions, but if you were using RadioBOSS before version 6.0 you could have APEv2 and it's slower).
• Organize the library, if it's really huge (100K+ records), and categories only use a tiny subset of it, you can create smaller libraries to fit the category needs. It's for situations where you filter out 90% of the tracks, it will spend a lot of time reading information for all those tracks.

When I'm not using Additional Priorities Rules, it's really quick to generate, but when I put between 1 and 5 rules it's really slow... I think I'm not alone in this case.

I don't have a SSD, I have a Raid 5 on 3 disk

I'm using Rbdata, not SQLite because I have 2 studios running in the same time on two different pcs, for backup and broadcast rescue.

I have approximately, 8000 records.

It was just to inform you, I can understand if you can't do anything more to optimize generation latencies

Best Regard dear Dmitry

Altec