[MDEV-3550] LP:1035245 - xtradb constant cpu load / mariadb 5.2.12 Created: 2012-08-10 Updated: 2012-10-04 Resolved: 2012-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Goetz T. Fischer (Inactive) | Assignee: | Elena Stepanova |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
|
machine specs: CPU: Intel(R) Core(TM)2 CPU E8400, 3.00GHz basic server installation, no X, no special hardware. only default debian packages and fully updated. mariadb 5.2.12 source package so i went ahead and tried a completely vanilla installation. used the my-medium.cnf and the following commands to get started from within the inst. dir:
all fine so far. now to the actual PROBLEM REPORT: as soon as i add the following to the cnf the db is constantly causing almost 50% cpu load on both cpus without me doing anything at all: innodb doesn't work by default so i used that option. this is the only plugin i load in that cnf file. actually xtradb is the main reason why i picked mariadb. the second reason is i want to compile it with icc which i did after i encountered this very issue but just got the exact same problem. without xtradb everything seems fine. MariaDB [(none)]> SHOW PROCESSLIST;
---
--- MariaDB [(none)]> SHOW INNODB STATUS;
===================================== then i tried the latest mariadb 5.1.x and encountered the exact same problem. also tried a bunch of other things like a different config, different already existing db files ... all without any success, still the same cpu load issue. |
| Comments |
| Comment by Elena Stepanova [ 2012-08-12 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 You mentioned that "innodb doesn't work by default", but that's only because you didn't add it to your configure options, you should have run it with --with-plugins=xtradb . That said, I've built 5.2.12 with the same exact configure options as you mentioned, and started it presumably the same way, and didn't have a problem with CPU; but I have a different version of gcc and ubuntu instead of debian, so it's not a clean experiment of course. Does the same happen if you run a binary distribution, e.g. from a binary tarball? If it does, we can probably rule out the compiler version or options. Thanks. |
| Comment by Goetz T. Fischer (Inactive) [ 2012-08-12 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 > Does the same happen if you run a binary distribution, e.g. from a binary anyhow thanks for the reply, will update this as soon as i finished the tries with a binary package ... |
| Comment by Goetz T. Fischer (Inactive) [ 2012-08-12 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 |
| Comment by Elena Stepanova [ 2012-08-13 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 I've been wondering if there is any particular reason you are choosing 5.1/5.2 over higher versions? Not that it should not work, just maybe you would have had a better luck with 5.5, since XtraDB/InnoDB has gone long way from 5.1-based versions to 5.5?.. |
| Comment by Elena Stepanova [ 2012-08-13 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 Could you please take a look, if you've ever seen anything like this or happen to know what might cause this? |
| Comment by Goetz T. Fischer (Inactive) [ 2012-08-14 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 |
| Comment by Axel Schwenke [ 2012-08-14 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 how exactly are you setting the mentioned "compiler options"? I'll try to reproduce your problem with mariadb-5.2.12. Please see if you have the 'mysqlbug' script from that build of yours and attach it. It contains all options used during compiling. |
| Comment by Goetz T. Fischer (Inactive) [ 2012-08-14 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 export CFLAGS='-mtune=core2 -mssse3 -O3' |
| Comment by Axel Schwenke [ 2012-08-22 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 I haven't been able to reproduce your problem, but would like to try investigate it further. I have two ideas so far: 1. is it possible that your system still suffers from the leap second problem? Try setting the system time like so: date -s "`date`" Background information: http://openquery.com/blog/2012-leap-second-linux 2. if the above does not change anything, please give us some more information. Start MariaDB so that it starts consuming cpu. Run: top -b -n 1 >top1.txt The first top run will run in process mode and should show mysqld on top (as it consumes most cpu). The second top run is in thread mode and will show individual threads. I hope all cpu is consumed by a single mysqld thread. Now create a full back trace of all threads in mysqld. For that lookup the mysqld PID (first top run) and run: gdb -ex "set pagination 0" -ex "thread apply all bt" -batch -p <PID> >mysqld-all-bt.txt (replace <PID> with the mysqld pid) zip all 3 files and attach the zip to this report. |
| Comment by Goetz T. Fischer (Inactive) [ 2012-08-22 ] |
|
Re: xtradb constant cpu load / mariadb 5.2.12 thanks for all the help!! |
| Comment by Rasmus Johansson (Inactive) [ 2012-08-24 ] |
|
Launchpad bug id: 1035245 |