We are using mysql 8.0 and also running 5.7 in some environment. We found our mysql 5.7 running fine on mostly environment but we are facing high CPU usage for 8.0. I didn't find anything in slow_query_logs, show processlist, persistent connections removed from PHP.
Same database dump working fine on mysql 5.7. I would really appreciate your quick suggestions.
Is mysql 8.0 is stable for live/production? please also share your thoughts.
Related
I would like to get some opinions on the comparison to install Mysql 8.0 in Windows Server and Ubuntu.
A lot of people recommend to run MySQL 8.0 on Linux/Ubuntu platform for better performance. In general, is there any performance degradation running Mysql 8.0 in Windows server?
Where can I get some reference on the comparisons?
I found this other SO post. here. I personally prefer Linux because there is less overhead in general as an operating system. They don't call it the LAMP stack for nothing, you know?
I currently host around 400 websites and would like to migrate from MySQL 5.5 to MariaDB 10. The server is running WHM/cPanel 11.58 (CloudLinux).
I see the option to change the installation but, before I go ahead and do it, I would like to know whether it's a "straightforward" process. I am struggling to find any information online that is clear cut and explains whether MySQL databases/tables are compatible 100% with MariaDB.
Yes, it's possible to upgrade it but I will suggest you first upgrade your mysql version to 5.6 and then upgrade it to MariaDB, Also before upgrading your mysql verison I will suggest you please take backup of your all databases in .sql format.
I am bit novice in some aspects here and no related information found...
I have an AWS instance with mysql client installed at 5.5 version. And also an RDS db instance with mysql 5.6 (in order to use t2.micro). I don't think so but, could this in your opinion/experience produce some kind of trouble when requesting queries (via PHP, specifically Symfony2) between them?
I hope it is no; but if yes, is strictly necessary then to upgrade my mysql client in the instance or there is any other way to use t2.micro with mysql server at 5.5?
Any guidance or related experience would be much appreciated.
See Upgrading from MySQL 5.5 to 5.6:
Note particularly any changes that are marked Known issue or
Incompatible change.
That said, your client app should be able to use 5.6 safely, and you got it right, that is required to use db.t2.micro instances.
I've scoured the MySql website to see if they have compatibility listings for MySQL Workbench, but have not found anything. Does anyone know if 6.0.x can connect to 5.5.x databases? I'd rather not install and then have to roll back.
MySQL Workbench can connect to most MySQL server versions, but that is probably not the primary question. You should rather ask what minimum version it can work with. MySQL Workbench requires at least MySQL 5.0 and can work with any MySQL server after that (including the new 5.7). Some features like authentication plugin or performance schema support require higher server versions, though.
RDS supports MySQL 5.5 and offers a lot of automated feature such as scaling up, expanding disk space, and upgrading the minor version of the database (e.g., from 5.1.49 to 5.1.50). However, is there a way to upgrade from 5.1.x to 5.5, either through the command line tools or the web GUI?
Good news, everyone! Amazon RDS now supports point-and-click upgrade from MySQL 5.1 to 5.5
The RDS FAQ says:
Currently, a direct upgrade from MySQL 5.1 to MySQL 5.5 is not supported.
so you'll have to do it the more traditional way.
For example a simplistic approach would be to start a 5.5 RDS instance and pipe the 5.1 database into it like this:
mysqldump -h mysql5.1.database.host database_name|mysql -h mysql5.5.database.host
then switch to using the 5.5 instance.
Of course, this would be slow for a large database and you will need to avoid writes to the source database during the transition.
Migrating from 5.1 to 5.5 is now available via the AWS Management Console.
I don't know when it was added, but it must've changed recently.