Replies: 2 comments 8 replies
-
Hi @addatwork, And on other hand you need to understand that -r and -F have similar outcomes but they are not the same. When you load a table, there other things to take into account like --innodb-optimize-keys which will split the table in 3 pieces when possible. It will create the table with only the columns and primary key, then it will add the secondary index and finally it will add the constraints. Why don't you share the restore logs? so I can understand why you are not able to get the performance you should. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your response. Here's the restore log using -r (i've tried my best to anonymize some of the names, sorry, i know it's going to be hard to follow) As you can se the total restore time is 127min. Without chunking and with 20 threads i get around 80 min. |
Beta Was this translation helpful? Give feedback.
-
I have a backup system where a few tables make up for the large majority of the content. Lately I've been playing with dividing those large tables using rows or file chunks. I have some questions.
Beta Was this translation helpful? Give feedback.
All reactions