YOUR QUERY
SELECT post.postid, post.attach FROM newbb_innopost AS post WHERE post.threadid = 51506;
At first glance, that query should only touches 1.1597% (62510 out of 5390146) of the table. It should be fast given the key distribution of threadid 51506.
REALITY CHECK
No matter which version of MySQL (Oracle, Percona, MariaDB) you use, none of them can fight to one enemy they all have in common : The InnoDB Architecture.
CLUSTERED INDEX
Please keep in mind that the each threadid entry has a primary key attached. This means that when you read from the index, it must do a primary key lookup within the ClusteredIndex (internally named gen_clust_index). In the ClusteredIndex, each InnoDB page contains both data and PRIMARY KEY index info. See my post Best of MyISAM and InnoDB for more info.
REDUNDANT INDEXES
You have a lot of clutter in the table because some indexes have the same leading columns. MySQL and InnoDB has to navigate through the index clutter to get to needed BTREE nodes. You should reduced that clutter by running the following:
ALTER TABLE newbb_innopost
DROP INDEX threadid,
DROP INDEX threadid_2,
DROP INDEX threadid_visible_dateline,
ADD INDEX threadid_visible_dateline_index (`threadid`,`visible`,`dateline`,`userid`)
;
Why strip down these indexes ?
- The first three indexes start with threadid
threadid_2
and threadid_visible_dateline
start with the same three columns
threadid_visible_dateline
does not need postid since it's the PRIMARY KEY and it's embedded
BUFFER CACHING
The InnoDB Buffer Pool caches data and index pages. MyISAM only caches index pages.
Just in this area alone, MyISAM does not waste time caching data. That's because it's not designed to cache data. InnoDB caches every data page and index page (and its grandmother) it touches. If your InnoDB Buffer Pool is too small, you could be caching pages, invalidating pages, and removing pages all in one query.
TABLE LAYOUT
You could shave of some space from the row by considering importthreadid
and importpostid
. You have them as BIGINTs. They take up 16 bytes in the ClusteredIndex per row.
You should run this
SELECT importthreadid,importpostid FROM newbb_innopost PROCEDURE ANALYSE();
This will recommend what data types these columns should be for the given dataset.
CONCLUSION
MyISAM has a lot less to contend with than InnoDB, especially in the area of caching.
While you revealed the amount of RAM (32GB
) and the version of MySQL (Server version: 10.0.12-MariaDB-1~trusty-wsrep-log mariadb.org binary distribution, wsrep_25.10.r4002
), there are still other pieces to this puzzle you have not revealed
- The InnoDB settings
- The Number of Cores
- Other settings from
my.cnf
If you can add these things to the question, I can further elaborate.
UPDATE 2014-08-28 11:27 EDT
You should increase threading
innodb_read_io_threads = 64
innodb_write_io_threads = 16
innodb_log_buffer_size = 256M
I would consider disabling the query cache (See my recent post Why query_cache_type is disabled by default start from MySQL 5.6?)
query_cache_size = 0
I would preserve the Buffer Pool
innodb_buffer_pool_dump_at_shutdown=1
innodb_buffer_pool_load_at_startup=1
Increase purge threads (if you do DML on multiple tables)
innodb_purge_threads = 4
GIVE IT A TRY !!!
I'm not great with recursion either, so don't feel bad. I've had success with structures similar to the following. It's not elegant, but you can see exactly what's going on. Basically you need to gather all the possible values to evaluate against both ID and ParentID for a given ParentID value. This solution assumes integer values. It will get a little more tricky with alphanumric values. The nice thing about this is you can run it as is or modify it to display a hierarchical ordering.
--create the table for the example
IF OBJECT_ID('tbl_RecursiveExample','U') IS NOT NULL
DROP TABLE tbl_RecursiveExample
CREATE TABLE tbl_RecursiveExample
(
ID INT
, ParentID INT
)
INSERT tbl_RecursiveExample
VALUES (1,NULL)
, (2,1)
, (3,1)
, (5,1)
, (5,4)
, (5,6)
, (8,6)
, (7,9)
, (9,10);
--change the value to the parentID you are interested in
DECLARE @ParentIDVal INT=10;
WITH
cteFirstRelationship --Top level relationships
AS
(
SELECT ID RelatedIDs
FROM tbl_RecursiveExample
WHERE ParentID = @ParentIDVal
UNION
SELECT ParentID
FROM tbl_RecursiveExample
WHERE ID = @ParentIDVal
),
cteSecondRelationship --secondary relationships
AS
(
SELECT ID RelatedIDs
FROM tbl_RecursiveExample t
JOIN cteFirstRelationship cf ON cf.RelatedIDs=t.ParentID
UNION
SELECT ParentID
FROM tbl_RecursiveExample t
JOIN cteFirstRelationship cf ON cf.RelatedIDs=t.ID
)
--possible add another level if needed
SELECT DISTINCT t.* --> Needed due to the match of both values
FROM tbl_RecursiveExample t
JOIN
(
SELECT RelatedIDs from cteFirstRelationship
UNION
SELECT RelatedIDs from cteSecondRelationship
)r ON r.RelatedIDs = t.ID OR r.RelatedIDs = t.ParentID
Best Answer