maria-discuss team mailing list archive

[Vladislav Vaintroub <vvaintroub@xxxxxxxxx>]

Oh ok, so it is a “maxi” dump.  But stull ,when you just start the service, the most of the memory allocated by the process  is zeroed , thus zipping the dmp should  I think make it much smaller.
 
You can share via Google drive, sure.



From: Peter Laursen
Sent: Saturday, January 20, 2018 5:23 PM
To: Vladislav Vaintroub
Cc: Maria Discuss
Subject: Re: [Maria-discuss] MariaDB 10.3.4 consumes extremely much CPUonWindows.

It happens always and immediately when I start the 10.3.4 mysqld process (as a service with "net start .." or from Control Panel .. Administration .. Services).  I think one dump will do as it is esactly the same thing everytime.

The dump is 4.6 GB. I just have to figure out how to transfer it!  Is a shared link to Google Drive OK (it is uploading now)? 

On Sat, Jan 20, 2018 at 5:14 PM, Vladislav Vaintroub <vvaintroub@xxxxxxxxx> wrote:
Hi Peter,
Could you take a 2-3 different process dumps , when it happens?
You do this by switching to “Detail” tab in Task manager, then mysqld.exe, rightclick, “Create dump”, and mysqld.DMP will be stored in temp directory. 
 
Could you then attach  minidumps  somewhere (ideally to a new bug in our  JIRA https://jira.mariadb.org/secure/Dashboard.jspa, ; but in case you do not have an account you can also send them to me so I can create a bugreport on your behalf)
 
Thanks!
 
From: Peter Laursen
Sent: Saturday, January 20, 2018 2:51 PM
To: Maria Discuss
Subject: [Maria-discuss] MariaDB 10.3.4 consumes extremely much CPU onWindows.
 
On a 4-core (4 physical, 8 logical cores), 3.5 Ghz box, MariaDB 10.3.4 consumes typically 35-40% of available CPU even when completely idle according to Task Manager. Please see image.
 
I cannot tell if previous 10.3 versions also did, as I don't have 10.3 running constantly in the backgorund. I just observed this now.  This does not happen with MariaDB 10.1, MariaDB 10.2, MySQL 5.6, MySQL 5.7 and MySQL 8.0 (all those I have starting with Windows on this box), where the CPU-load is neglible unless the server is "doing real work".
 
As a result, the CPU clock frequency is always highest possible 3.5 Ghz (this CPU model is a 4th generation Intel with the option to scale down CPU frequency to around 40-50% of max. when there is no need for more) when MariaDB 10.3.4 is running.
 
 
 
-- Peter
-- Webyog