You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you add multiple threads to restore at the same time? A few days ago, I backed up a database with many tables. The database was backed up for 7 minutes and the backup file size was 2.4G, but the entire database was restored for 90 minutes. I watched the entire restoration process, one at a time. Table, can it be added to support restoring multiple tables at the same time?
The text was updated successfully, but these errors were encountered:
Multiple threads for the restoration of database might not be the good idea. Import mechanism at MySQL is writing data into the storage drive. Storage drive works best with 1 task at the time. Multiple writing queue will not accelerate but slow down the whole process.
I will try to do some research on this issue at my next available time and see whether the code can be optimized to run even faster for the import process.
Multiple threads for the restoration of database might not be the good idea. Import mechanism at MySQL is writing data into the storage drive. Storage drive works best with 1 task at the time. Multiple writing queue will not accelerate but slow down the whole process.
I will try to do some research on this issue at my next available time and see whether the code can be optimized to run even faster for the import process.
Thank you very much, and look forward to solving the problem of slow restoration of large databases.
Can you add multiple threads to restore at the same time? A few days ago, I backed up a database with many tables. The database was backed up for 7 minutes and the backup file size was 2.4G, but the entire database was restored for 90 minutes. I watched the entire restoration process, one at a time. Table, can it be added to support restoring multiple tables at the same time?
The text was updated successfully, but these errors were encountered: