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
Describe the bug
When you have over several hundred thousand Data Sources or Graphs, additional sort variables should be tuned including 'innodb_sort_buffer_size' and 'sort_buffer_size' to have the sort indexes created in memory.
To Reproduce
Steps to reproduce the behavior:
Source Data Sources by Name Cache for very large number of Data Sources
Adjust the innodb_sort_buffer_size to a larger number like 200M
Restart mariadb and warm up the table
Sort again and see the performance difference
Expected behavior
Better performance.
Additional context
There are notes that starting with MySQL 5.6, the sort buffer size is dynamic upto the max settings, so it does not have the same significant effect as it used to have in prior MySQL versions.
The text was updated successfully, but these errors were encountered:
We have a recommendation for this right now, but since it's a client setting, we have to be careful. Therefore, I'm considering this one closed/complete.
netniV
changed the title
For large systems, the sort buffer should be optimized for large tables
The innodb sort buffer should be optimized for large tables
Dec 31, 2022
Describe the bug
When you have over several hundred thousand Data Sources or Graphs, additional sort variables should be tuned including 'innodb_sort_buffer_size' and 'sort_buffer_size' to have the sort indexes created in memory.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Better performance.
Additional context
There are notes that starting with MySQL 5.6, the sort buffer size is dynamic upto the max settings, so it does not have the same significant effect as it used to have in prior MySQL versions.
The text was updated successfully, but these errors were encountered: