For springMVC + Hibernate + Mysql backend, Hikaricp connection pool, the maximum number of connections with eight, four cores, 4 gb of memory to use connection, wrote an interface, content is a new object and then save, 30 times with jmeter500 concurrent circulation call this interface, when concurrency is 5.7 8.5 seconds, a total of 15000 data, after upgraded to 8.0.13, this time into 11 seconds, utf8 encoding, introduction is not to say that will change fast, later found mysql8 default open binlog, off me, but did not change and is not stable, after I restart the Mysql service, the first test, the fastest, slowed after, the bosses to give directions, is why ah

CodePudding user response:

Don't sink,,,

CodePudding user response:

Don't sink,,,

CodePudding user response:

Is there a big comment ~

CodePudding user response:

Excuse me, I also used 8, look from the configuration file no problem, when your current environment and 5.7 the same environment?
Inside the database data and index and the same as before?
Theory is the first run slow; The second run faster, because there is no thermal data, running a database for the first time the second run because of the thermal data, so will be faster,

CodePudding user response:

Don't say it's only used 5.7 to 8 but look forward to

CodePudding user response:

Good is good, recently installed 8, 0 to play, looking forward to you the little mice performance

CodePudding user response:

I said it's the same with 5.7 seconds to generate more than 30 orders, in after 8 second never more than ten pens, and then I change the data source of project 5.7 is again good, pit it feel (I'm a local database, use a notebook to test)

CodePudding user response:

Database 5.7, and I just wrote a new mybatis cycle data, in 5.7 most has more than 60 data, but by the time 8.0 only less than ten data, feeling the pit is too big, is a simple new, performance measurement can also be the way you are?

CodePudding user response:

Just understand the mysql8.0 it does not support myisam, only the innodb, myisam efficiency faster than innodb, so in the new data will be slow

CodePudding user response:

references 9 f u010494101 response:

just understanding the mysql8.0 it does not support myisam, only the innodb, myisam efficiency faster than innodb, so in the new data will slow

I tested the local mysql8.0.11 (Ver 8.0.11 for macos10.13 on x86_64 (MySQL Community Server - the GPL)) support myisam mode, I don't know what you said is which version does not support?

CodePudding user response:

Project to solve the building Lord, our company use mysql8, want to know you is how to solve

CodePudding user response:

references 9 f u010494101 response:

just understanding the mysql8.0 it does not support myisam, only the innodb, myisam efficiency faster than innodb, so in the new data will be slow

thumb up to you is for you to have a closer look at the mysql 8.0 is not slow

CodePudding user response:

Is there any follow-up the building Lord, I built two database server, a platform running 5.6 a table 8.0 also found that write speed, 200 w record about 500 m, the amount of data is slower than the 5.6 8.0 for more than 30 seconds, the landlord to find out the solution to insert to modify the cause of the slow, I test to delete 8.0 than 5.6

CodePudding user response:

8.0 without the query cache