Support - MySQL 5.7
MySQL 5.7 is 3x faster than 5.6
Check details:
https://www.oracle.com/corporate/pressrelease/mysql-5-7-ga-101915.html
This functionality was added in Plesk ‘Onyx’ 17.0
We suggest you to upgrade to Plesk ‘Onyx’ and check it out.
https://docs.plesk.com/release-notes/17.0/software-requirements/
— SU
-
Ermi commented
Still waiting ...
-
banditetr commented
Hi I have Onyx 17 and there is no possibility to upgrade MySQL to Version 5.6 or 5.7 without manual installation
-
Anonymous commented
Hey guys - we really need this ASAP. Magento 2.1 requires it and we cannot move any further until its sorted.
-
Anonymous commented
MySQL 5.7 or at least 5.6 is overdue. Please can You implement it asap.
Thanx -
Pim Effting commented
This is a system administrator issue, not a Plesk issue.
-
Manu-K commented
@Plesk Staff: is there any plan for the implementation?
-
sait ersoy commented
s
-
Mehdi commented
Please add support for mysql 5.7, or at least mysql 5.6 - Wordpress is the most used cms in the world guys and recommends 5.6 - security is very important for everybody I hope ;-)
-
Cool Dark commented
I think the wish is outdated as MySQL 5.7 is here. Please vote there:
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/10675545-support-mysql-5-7 -
trialotto commented
@Everybody,
There is this performance issue with older MySql versions, which can be (very) easily resolved by optimizing the configuration of the MySql server.
In addition, in the MySql versions 5.6.6 and higher, one can get some issues related to innodb_buffer_pool_size and innodb_buffer_pool_instances.
In general, the "max memory usage" of (every version of) MySql server can become a serious problem on VPSes: if the InnoDB Buffer Pool is 50% of the total memory (RAM), the OS can or will use swap space, which is bad.
Reducing the "max memory usage issue" by increasing the "innodb_buffer_pool_instances" value will resolve this, but this is somewhat problematic in MySql versions 5.6.6 or higher.
However, increasing the innodb-thread-concurrency will make MySql version 5.6.x more or less comparable to MySql version 5.7.x, but that is a rough indication.
In summary, it is the question whether one should want MySql versions 5.6.x and 5.7.x.
After all, a good configuration will make any MySql version more preformant that earlier versions.
The ACTUAL PROBLEM is NOT performance, but SECURITY.
The MySql versions 5.6.x and 5.7.x are better patched.
NOTE THAT MySql version 5.5.x contains roughly 200 CVE security vulnerabilities.
So, why not upgrade to the supported version 5.6.x?
In my opinion, that is better than discussing 5.7.x support.
Regards....
-
JC commented
Hello,
The 2.1 version of Magento requires MySQL 5.7
Thank you in advance.
-
Anonymous commented
This feature is needed. Wordpress.org is recommending user to leave and find hosted that supports mysql 5.6 or higher.
-
Madalin Ignisca commented
on shared hosting, on servers with around 8 threads and 32gb ram, mysql 5.5 offers higher performance then 5.6 or 5.7.
well, differences are in ms, so for a web agency, makes no difference.
-
Madalin Ignisca commented
Those benchmarks are for heavy servers (minimum 16 threads, more then 32GB ram).
Support should be to allow 5.5 (best on small servers), 5.6 or 5.7.
-
Max commented
Always happy to see Mysql upgrades HOWEVER 3x faster but doesn't detail the specifications.
-
David commented
Users of control panel tools are not server admins. You should work with Oracle to provide a 1 click install of MySQL Enterprise. You can then work with Oracle to earn from the £3400 support contract. My own Plesk panel was damaged when following Oracle's own instructions. The customer needs confidence that it will install and can be updated without having to access any command line / root access shells. This is similar to your YUM tickets for Centos, Plesk must be in charge of everything, rather then some via Plesk and others on the server.
-
Izaim O. commented
No, MariaDB 10.1 is faster!
-
Marco Marsala commented
Actually MySQL from the official Oracle repo is not supported but the corresponding KB article was updated only after I reported the issue.
Many users updated MySQL using that repo - before the KB got updated - and now they have broken servers.Supporting MySQL from Oracle repo is simple because they just use a different file name for the unixODBC .so (mind the w at the end) and path of the socket (/tmp/mysql.sock). Indeed, the compatibility is now achieved manually creating soft or hard links between real and expected (by Plesk) paths.
-
Anonymous commented
+3 for new MySQL