• English
  • Deutsch
  • Español
  • Русский
Professional Radio Automation at a price you can afford.Professional Radio Automation at a price you can afford.
RadioBOSS box
RadioBOSS makes automating your broadcast to the world, your business or shop professional, simple, affordable, reliable.

Author Topic: MySQL vs SQLite  (Read 1360 times)

0 Members and 1 Guest are viewing this topic.

pety

  • Experienced user
  • Posts: 1251
MySQL vs SQLite
« on: June 13, 2019, 03:44:55 AM »
I would like to test Databases in RadioBOSS.
Which is faster and stable too?
SQLite looks more portable, but I know that MySQL is heavier (i use it in web development). MySQL needs more resources.
Any advice?

nelson c

  • Experienced user
  • Posts: 1439
    • Radio Music
Re: MySQL vs SQLite
« Reply #1 on: June 13, 2019, 12:32:56 PM »
We have been working with MySQL for months, and the truth is 100% stable.  and the performance is excellent.

pety

  • Experienced user
  • Posts: 1251
Re: MySQL vs SQLite
« Reply #2 on: June 13, 2019, 09:03:02 PM »
We have been working with MySQL for months, and the truth is 100% stable.  and the performance is excellent.
Thanks a lot !
What about system requirements?

djsoft

  • Administrator
  • Posts: 10386
    • http://www.djsoft.net
Re: MySQL vs SQLite
« Reply #3 on: June 14, 2019, 02:48:50 AM »
SQLite looks more portable, but I know that MySQL is heavier (i use it in web development). MySQL needs more resources.
Any advice?
SQLite does not require any configuration, just turn it on in RadioBOSS settings and that's it. MySQL requires you to install the database (MySQL or, better, MariaDB) and input connection information into RadioBOSS.

In terms of resources, there's no difference between the two, we've tested it on huge databases and it performed very well.
Dmitry  •  DJSoft.Net Team  •  Email: support@djsoft.net

pety

  • Experienced user
  • Posts: 1251
Re: MySQL vs SQLite
« Reply #4 on: June 14, 2019, 09:07:29 AM »
In terms of resources, there's no difference between the two, we've tested it on huge databases and it performed very well.
It seems SQLite will be the choice. Thanks a lot !

pety

  • Experienced user
  • Posts: 1251
Re: MySQL vs SQLite
« Reply #5 on: January 11, 2020, 07:58:32 PM »
I selected SQLite.
I made some libraries (XML).


If RB stores Libraries in XML files where and how SQLite works?

djsoft

  • Administrator
  • Posts: 10386
    • http://www.djsoft.net
Re: MySQL vs SQLite
« Reply #6 on: January 14, 2020, 03:28:09 AM »
If RB stores Libraries in XML files where and how SQLite works?
SQLite is used to store additional information (playcount, custom fades etc). In the future, we'll get rid of XML completely and use SQLite only.
Dmitry  •  DJSoft.Net Team  •  Email: support@djsoft.net

pety

  • Experienced user
  • Posts: 1251
Re: MySQL vs SQLite
« Reply #7 on: January 14, 2020, 04:51:08 AM »
SQLite is used to store additional information (playcount, custom fades etc). In the future, we'll get rid of XML completely and use SQLite only.
Excellent, thanks! Now displaying tracks with "Read additional track information" is very fast on my laptop. I'll check in production too.