MariaDB mysql server addon

Roughly 6.8 seconds for 8230 for that view is much better than 30 seconds. On a PC+SSD setup it's still sluggish (MySQL 5.x results return instantly), on a RPi-like device with SQLite, it's "just about acceptable" for me. Five seconds is a mental barrier. But it should still go faster IMO.

So I'd say it's an improvement, if all the other query stuff still works as advertised.

After the import, I would be guessing the mariadb cache isn't big enough the whole database and thus for "that query" to go fast, but maybe it is?

What if you run the query 5 times or so, 1 every minute. Is it constantly resulting in the 6.789s regions?

I noticed the optimizer_search_depth setting earlier and had some thoughts on it but I hadn't changed it yet.

I'm gonna be AFK for a couple hours, will test later tonight.

vpeter: Disable the optimizer_search_depth parameter via a hashtag in my.cnf.

I thought 0 as value would also work but it does slow down things.

I still get hiccups sometimes but apparently the MySQL Workbench tool is at fault there.

The query is now returning data quickly:

6255 records in 0.173s

9320 records in 0.224s

I just installed Raspbian Stretch & LAMP on a RPi3B+/SSD setup. It installs MariaDB 10.1.37, and the optimizer_search_depth parameter is nowhere to be found in its my.cnf file.

Also, the episode_view from my Kodi video database is done under a second: 9665 rows in 0.853, which is not bad either in my view.

I will test the updated mariadb addon for generic later on.

vpeter  CvH Okay, on my Intel-Celeron box I uninstalled the old MariaDB add-on, along with its settings. (I haven't double-checked if they were gone..) Then installed the service.mariadb-9.0.101.zip that cvh provided, imported my latest mysqldump, and did the episode_view query.

I got 9665 records in 0.210 secs, so I guess we can call this myth now busted.

AFAIK for mysql server, password encryption is a one-way street. If it were that easy, hackers would have a blast.

Only if you press the OK button, the new password values will be stored, otherwise the old/current ones will be used.

If the addon update auto-changes the new passwords, then there would be problem.

If you updated from one of the initial test versions then passwords might be overwritten (once) as the password changes were added shortly before merging and the first run of the current addon would be treated as a first-run and would create/set passwords. However once you're on the current addon that shouldn't happen again. If it does, there's a bug to be investigated.

If you were to re-update your add-on from the Kodi packages cache, wouldn't the same thing happen: passwords being overwritten?