2014-07-12, 22:20
Team,
it appears to me that the DB has some potential space for improvement.
Jus timporting my library from a single XBMC implementation MySQL reported those data as RED (aka not good):
Handler read rnd
362.9 k The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler read rnd next
680.4 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Connections
22.9 k The number of connection attempts (successful or not) to the MySQL server.
Select full join
7 The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Slow queries
1.1 k The number of queries that have taken more than long_query_time seconds.Documentation
Sort merge passes
88 The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
Table locks waited
325 The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
I think we need to seriously work on DB and Library to optimize this. The result can be outstanding.
Who is in charge of the DB part? how we can work on it?
M
I worte this as to import my library it takes more than 12 HOURS! reading all the information from local NFO files fully compiled and correct (from EmberMediaManager)...
it appears to me that the DB has some potential space for improvement.
Jus timporting my library from a single XBMC implementation MySQL reported those data as RED (aka not good):
Handler read rnd
362.9 k The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler read rnd next
680.4 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Connections
22.9 k The number of connection attempts (successful or not) to the MySQL server.
Select full join
7 The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Slow queries
1.1 k The number of queries that have taken more than long_query_time seconds.Documentation
Sort merge passes
88 The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
Table locks waited
325 The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
I think we need to seriously work on DB and Library to optimize this. The result can be outstanding.
Who is in charge of the DB part? how we can work on it?
M
I worte this as to import my library it takes more than 12 HOURS! reading all the information from local NFO files fully compiled and correct (from EmberMediaManager)...