fil_open_log_and_system_tablespace_files not multithreaded

Bug #1324956 reported by Yves Trudeau
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Won't Fix
Undecided
Unassigned
5.5
Won't Fix
Undecided
Unassigned
5.6
Triaged
Medium
Unassigned
5.7
Triaged
Medium
Unassigned

Bug Description

More and more deployments of MySQL have very large number of Innodb tablespaces, opening 100k tablespaces on a single thread, even if the storage is a large raid 10 array, proceed at about 200/s (15k rpm drives) which takes a long time, ~8min. This process should be multithreaded using the innodb_io_read_threads to better utilize large raid arrays.

tags: added: innodb performance upstream
removed: slow startup
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Yves,

Would you mind to report this to upstream MySQL or should I?

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1506

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.