Will the advent of chatGPT mean that MySQL veterans will lose their jobs?

This is Onikai (@fat47) from the Service Reliability Group (SRG) of the Technology Division.
#SRGThe Service Reliability Group primarily provides comprehensive support for the infrastructure surrounding our media services, focusing on improving existing services, launching new ones, and contributing to open-source software (OSS).
This article is located within SRG.DBWGThe DB Working Group is releasing database-related materials that it provides to the entire company.
I hope this is of some help.
 

Introduction


I apologize for the overly general title that seems to be following a trend.
In this article, I'd like to consider how practical it is at this point to provide ChatGPT, BingAI, and other systems with the contents of my.cnf and receive advice on tuning the settings.
💡
ChatGPT and similar tools may use your input data for training purposes. Please refrain from entering personal or confidential information.
 

Question content


"Below is the my.cnf configuration file used with MySQL 5.7. Please tell me all the items that might be problematic. If you need any additional information to get the best results with this task, please ask questions."
 

Traps scattered throughout the configuration file


The following are some parameters that I would like the AI ​​to point out as having configuration errors or other issues:
Setting item nameexplanation
For large buffer pools, it is advisable to split them.
It's ON by default, but I've intentionally disabled it.
This setting is always enabled in MySQL 5.7.10 and later.
Starting with MySQL 5.7, Barracuda is the default parameter. It is a deprecated parameter in MySQL 5.7.
This setting reduces the frequency of writing to the InnoDB log.
utf8mb4 is preferable to utf8 (utf8mb3).
 

answer


chatGPT Free Version (GPT-3.5)

7 points raised
query_cache_size=0
innodb_buffer_pool_instances

Bing AI(GPT-4)

7 points raised
query_cache_size=0
It's good that it also provides recommended values ​​for other settings.

ChatGPT Plus(GPT-4)

Ten points were raised.
query_cache_size=0
There is also a lot of information on other topics.
Some people even advised me to use something newer than MySQL 5.7 (lol).
 

I tried three and created a comparison chart.


×= No comments were made regarding the item.
= There was a comment about the item, but I'm not sure if the content is correct.
= There are some points raised, and the content seems to be mostly correct.
Setting item namechatGPT(GPT-3.5)BingAI(GPT-4)ChatGPT Plus(GPT-4)
innodb_buffer_pool_instances = 1×
innodb_doublewrite=0
innodb_support_xa = OFF
innodb_file_format×××
innodb_flush_log_at_trx_commit = 0
character-set-server = utf8×××
innodb_support_xa
innodb_file_format
character-set-server = utf8

In conclusion


While the feedback I received wasn't entirely satisfactory, I think it could be useful as a starting point for tuning.
At this point, it seems we still need the expertise of MySQL enthusiasts, so I'm somewhat relieved (?), but I'm looking forward to the future advancements in AI.
 
SRG is looking for new team members. If you are interested, please contact us here.