Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-33743

Feature request - a kind of "memory configuration tracker(?)"

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • N/A
    • None
    • Server
    • None
    • Any.

    Description

      Hi.

      When user have big memory like 1TB or more than actually require to run the MariaDB,
      and implemented db system ready to run.
      if user turn of the feature(by config file or any of method not set detail settings) without specifying any of memory configs(key_buffer_size,query_cache_size,tmp_table_size,innodb_buffer_pool_size,innodb_additional_mem_pool_size,innodb_log_buffer_size,max_connections, etc.) and run in live environment the db for a while. Then the db, record each of memory usage/peak level interval(minutes or hours or any) into a table until user turn off.
      Then db admin/user review the status of memory usage pattern, and finally fix/set the limit/threshold into config.ini file.

      Really need that. current traditional way is so...weird that maually set the each values in blind repeatly.

      You guy employee AI logic to record or automatically set the values for self monitoring/adjusting. In any of way, really need the feature to self manage the system to rid tired/sick tuning effort.
      The admin/user only set/give the single value that max memory usage limit in GB. For example, set the max memory value as 256GB in config, the db find the optimal setting automatically ontime or periodically automatically.

      Attachments

        Activity

          People

            Unassigned Unassigned
            npdmailing@gmail.com Mitchell Lee
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.