Re: MySQL optimization for testing purpose
Tested with:
tmp_table_size = 512M
max_heap_table_size = 512M
But this did not help...
Note that I get similar symptoms with different versions of MySQL 8.0, 5.7 ( and MariaDB 10.3! ) ...
So I believe there is quite a serious problem in the server code. You might want to try to reproduce on your side with pure SQL, with a script that repeats CREATE TABLE, INSERT 1 row, SELECT the row, DROP TABLE. If you cannot repro, change the column type in CREATE TABLE statements, to cover all possible MySQL types...
Just a thought: Is it possible that the server detects that a process is going crazy by creating and dropping the same table many times, and decides to allocate less SQL processing by design? Or prevent attacks or so?
Seb
Subject
Views
Written By
Posted
1708
April 04, 2018 10:05AM
705
April 04, 2018 10:56AM
754
April 06, 2018 02:00AM
830
April 06, 2018 12:10PM
716
April 09, 2018 02:18AM
826
April 09, 2018 07:18AM
779
April 09, 2018 07:23AM
850
April 09, 2018 07:34AM
726
April 09, 2018 08:00AM
944
April 09, 2018 10:06AM
Re: MySQL optimization for testing purpose
742
April 10, 2018 08:24AM
758
April 10, 2018 10:27AM
710
April 10, 2018 11:07AM
Sorry, you can't reply to this topic. It has been closed.
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.