Re: FreeBSD 4.8 runaway MySQL 4.0.14
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Fri, 12 Sep 2003, Jeremy Zawodny wrote: > I think the best way to do this would be to provide the standard FreeBSD > build just like you do now and to also provide a LinuxThreads-enabled > build for people who really want it. I don't think you'd want to force > the LT requirement on everyone. > > But hopefully you were already thinking that too... Yes, that was my intention - we will continue to provide the default builds and add new packages with the suffix "-linuxthreads". Bye, LenZ - -- Lenz Grimmer <[EMAIL PROTECTED]> Senior Production Engineer MySQL GmbH, http://www.mysql.de/ Hamburg, Germany For technical support contracts, visit https://order.mysql.com/?ref=mlgr -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/YYR/SVDhKrJykfIRAsCaAJ9GQF6ln/ourJ9ApUejujcr4uZIQQCdEGyC Web63sWJ6dzexG+kEeCHlYM= =7rLZ -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: FreeBSD 4.8 runaway MySQL 4.0.14
On Fri, Sep 12, 2003 at 09:58:03AM +0200, Lenz Grimmer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > (please Cc: me directly, if you want to catch my attention - I don't > always follow this list very closely) Oops. Good point. > > It's always felt like FreeBSD became a second-class platform at MySQL AB > > when Tim left a few years back. At the time, he was the only MySQL > > developer using FreeBSD. But I don't know what the current state is > > there. > > We do have a few guys that use FreeBSD as their main development platform. > > Sorry if you got the impression that FreeBSD is considered "second-class" > - - this is definately not the case. Good to hear! > I'm more of a Linux Guy, but that does not really matter. :) I am too. :-) > > Or maybe we can strong arm the MySQL build folks (Hi, Lenz) into doing > > it? > > I'd be more than happy, if I knew how exactly this is done. I'll work with > Serg to get this configured for the next release. Excellent. I think the best way to do this would be to provide the standard FreeBSD build just like you do now and to also provide a LinuxThreads-enabled build for people who really want it. I don't think you'd want to force the LT requirement on everyone. But hopefully you were already thinking that too... Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 4 days, processed 179,586,914 queries (447/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: FreeBSD 4.8 runaway MySQL 4.0.14
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, (please Cc: me directly, if you want to catch my attention - I don't always follow this list very closely) On Thu, 11 Sep 2003, Jeremy Zawodny wrote: > On Thu, Aug 28, 2003 at 04:20:50PM -0400, Nick Gaugler wrote: > > > Thanks for the response. I really wish MySQL AB would compile FreeBSD > > binaries with LinuxThreads. It's really a pain when you find a bug, > > the first thing they ask is "have you compiled this yourself" when in > > this case you have no choice but to compile it yourself. > > Good point. That does suck, doesn't it? > > It's always felt like FreeBSD became a second-class platform at MySQL AB > when Tim left a few years back. At the time, he was the only MySQL > developer using FreeBSD. But I don't know what the current state is > there. We do have a few guys that use FreeBSD as their main development platform. Sorry if you got the impression that FreeBSD is considered "second-class" - - this is definately not the case. I'm more of a Linux Guy, but that does not really matter. :) > > Maybe Jeremy could compile "unofficial but recommended" binaries that > > MySQL AB would support more like official binaries? :) If he's got > > nothing better to do of course, he already puts in so much time to the > > MySQL community as is. > > I'll need to first confirm that our "Yahoo FreeBSD" is close enough to > "normal" FreeBSD that the binaries would work. I suspect it wouldn't be > a problem... > > But, yeah, it's not a bad idea come think of it. > > Or maybe we can strong arm the MySQL build folks (Hi, Lenz) into doing > it? I'd be more than happy, if I knew how exactly this is done. I'll work with Serg to get this configured for the next release. > I'm not sure if they're thinking that FreeBSD users already use ports, > so it's no big deal. Well, true. I must admit that this thought crossed my mind :) > But if so, that's not really compatible with their standard "are you > using our binaries" response... Agreed. We'll try to get this fixed for the next release. I assume it's not rocket science - I am simply not very familiar with the whole FreeBSD concept... Bye, LenZ - -- Lenz Grimmer <[EMAIL PROTECTED]> Senior Production Engineer MySQL GmbH, http://www.mysql.de/ Hamburg, Germany For technical support contracts, visit https://order.mysql.com/?ref=mlgr -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/YXyMSVDhKrJykfIRAqZXAJwJUaUghUSSX017nzmNmHb0MeAF6gCfRbvh a+yCq7K7Yd6S0FKnTRJ0bVk= =Qot0 -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: FreeBSD 4.8 runaway MySQL 4.0.14
On Thu, Aug 28, 2003 at 04:14:13PM -0400, Ken Menzel wrote: > Hi Nick, >This is due (so I am told) to a problem in FreeBSD threads. I have > this happen once in a while also. There have been some threads > changes for 4.9 but I am not sure there is any change in this. > > The common suggestion is to compile with LINUXTHREADS option using the > ports tree. This will solve that and give you better performance on a > multi CPU system. (cd /usr/ports/databases/mysql41-server; more > Makefile ) > or see http://jeremy.zawodny.com/blog/archives/000458.html You can probably eliminiate (or nearly eliminate) the problem by using skip-name-resolve in my.cnf on FreeBSD. That's the root of this problem, IIRC. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 4 days, processed 166,176,320 queries (450/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: FreeBSD 4.8 runaway MySQL 4.0.14
On Thu, Aug 28, 2003 at 04:20:50PM -0400, Nick Gaugler wrote: > Ken, > > Thanks for the response. I really wish MySQL AB would compile FreeBSD > binaries with LinuxThreads. It's really a pain when you find a bug, the > first thing they ask is "have you compiled this yourself" when in this > case you have no choice but to compile it yourself. Good point. That does suck, doesn't it? It's always felt like FreeBSD became a second-class platform at MySQL AB when Tim left a few years back. At the time, he was the only MySQL developer using FreeBSD. But I don't know what the current state is there. > Maybe Jeremy could compile "unofficial but recommended" binaries that > MySQL AB would support more like official binaries? :) If he's got > nothing better to do of course, he already puts in so much time to the > MySQL community as is. I'll need to first confirm that our "Yahoo FreeBSD" is close enough to "normal" FreeBSD that the binaries would work. I suspect it wouldn't be a problem... But, yeah, it's not a bad idea come think of it. Or maybe we can strong arm the MySQL build folks (Hi, Lenz) into doing it? I'm not sure if they're thinking that FreeBSD users already use ports, so it's no big deal. But if so, that's not really compatible with their standard "are you using our binaries" response... Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 4 days, processed 166,016,658 queries (450/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: FreeBSD 4.8 runaway MySQL 4.0.14
Ken, Thanks for the response. I really wish MySQL AB would compile FreeBSD binaries with LinuxThreads. It's really a pain when you find a bug, the first thing they ask is "have you compiled this yourself" when in this case you have no choice but to compile it yourself. Maybe Jeremy could compile "unofficial but recommended" binaries that MySQL AB would support more like official binaries? :) If he's got nothing better to do of course, he already puts in so much time to the MySQL community as is. Nick -Original Message- From: Ken Menzel [mailto:[EMAIL PROTECTED] Sent: Thursday, August 28, 2003 4:14 PM To: Nick Gaugler; [EMAIL PROTECTED] Subject: Re: FreeBSD 4.8 runaway MySQL 4.0.14 Hi Nick, This is due (so I am told) to a problem in FreeBSD threads. I have this happen once in a while also. There have been some threads changes for 4.9 but I am not sure there is any change in this. The common suggestion is to compile with LINUXTHREADS option using the ports tree. This will solve that and give you better performance on a multi CPU system. (cd /usr/ports/databases/mysql41-server; more Makefile ) or see http://jeremy.zawodny.com/blog/archives/000458.html Another option would be to update to FreeBSD 5.1 and use the new threading (not so easy). I personaly hope 4.9 will settle this down some as I don't see the need to go to LINUX Threads for a single proc machine! Best of Luck Ken - Original Message - From: "Nick Gaugler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 28, 2003 3:53 PM Subject: FW: FreeBSD 4.8 runaway MySQL 4.0.14 > I am running the binary installation of MySQL 4.0.14 on FreeBSD 4.8, all > MyISAM tables, and after alittle while mysqld will jump to 100% of my > CPU and go crazy. I've investigated SHOW INNODB STATUS, and as you can > see below, there is nothing happening with Innodb. Infact my Innodb > files have not even changed since I last restarted. But for some reason > MySQLd uses 100% of my CPU with no queries happening. I tried to run > ktrace and this was all I saw: > > > 30488 mysqld CALL gettimeofday(0x2846e288,0) > 30488 mysqld RET gettimeofday 0 > 30488 mysqld CALL poll(0x83b6000,0xc,0) > 30488 mysqld RET poll 0 > 30488 mysqld CALL poll(0x83b6000,0xd,0x126) > 30488 mysqld RET poll 1 > 30488 mysqld CALL gettimeofday(0x2846e288,0) > 30488 mysqld RET gettimeofday 0 > 30488 mysqld CALL poll(0x83b6000,0xd,0x126) > 30488 mysqld RET poll 1 > > With an occasional > > 30488 mysqld CALL poll(0x83b6000,0xd,0x126) > 30488 mysqld PSIG SIGPROF caught handler=0x2842562c mask=0x0 > code=0x0 > 30488 mysqld RET poll 1 > 30488 mysqld CALL gettimeofday(0x2846e288,0) > 30488 mysqld RET gettimeofday 0 > 30488 mysqld CALL sigreturn(0x83a9db8) > 30488 mysqld RET sigreturn JUSTRETURN > > > Has anyone experienced a runway mysqld on FreeBSD before? Is there > anything I can do to fix this or solve this problem? Below is show > innodb status\g > > = > 030828 14:36:37 INNODB MONITOR OUTPUT > = > Per second averages calculated from the last 16 seconds > -- > SEMAPHORES > -- > OS WAIT ARRAY INFO: reservation count 4, signal count 4 > Mutex spin waits 0, rounds 0, OS waits 0 > RW-shared spins 6, OS waits 3; RW-excl spins 1, OS waits 1 > > TRANSACTIONS > > Trx id counter 0 1280 > Purge done for trx's n:o < 0 0 undo n:o < 0 0 > Total number of lock structs in row lock hash table 0 > LIST OF TRANSACTIONS FOR EACH SESSION: > ---TRANSACTION 0 0, not started, OS thread id 299134976 > MySQL thread id 176926, query id 516226 localhost root > show innodb status > > FILE I/O > > I/O thread 0 state: waiting for i/o request (insert buffer thread) > I/O thread 1 state: waiting for i/o request (log thread) > I/O thread 2 state: waiting for i/o request (read thread) > I/O thread 3 state: waiting for i/o request (write thread) > Pending normal aio reads: 0, aio writes: 0, > ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 > Pending flushes (fsync) log: 0; buffer pool: 0 > 40 OS file reads, 4 OS file writes, 4 OS fsyncs > 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s > - > INSERT BUFFER AND ADAPTIVE HASH INDEX > - > Ibuf for space 0: size 1, free list len 0, seg size 2, > 0 inserts, 0 merged recs, 0 merges > Hash table size 34679, used cells 0, node heap has 0 buffer(s) > 0.00 hash searches/s, 0.00 non-hash searches/s > --- > LOG > --- > Log sequence number 0 4389
Re: FreeBSD 4.8 runaway MySQL 4.0.14
Hi Nick, This is due (so I am told) to a problem in FreeBSD threads. I have this happen once in a while also. There have been some threads changes for 4.9 but I am not sure there is any change in this. The common suggestion is to compile with LINUXTHREADS option using the ports tree. This will solve that and give you better performance on a multi CPU system. (cd /usr/ports/databases/mysql41-server; more Makefile ) or see http://jeremy.zawodny.com/blog/archives/000458.html Another option would be to update to FreeBSD 5.1 and use the new threading (not so easy). I personaly hope 4.9 will settle this down some as I don't see the need to go to LINUX Threads for a single proc machine! Best of Luck Ken - Original Message - From: "Nick Gaugler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 28, 2003 3:53 PM Subject: FW: FreeBSD 4.8 runaway MySQL 4.0.14 > I am running the binary installation of MySQL 4.0.14 on FreeBSD 4.8, all > MyISAM tables, and after alittle while mysqld will jump to 100% of my > CPU and go crazy. I've investigated SHOW INNODB STATUS, and as you can > see below, there is nothing happening with Innodb. Infact my Innodb > files have not even changed since I last restarted. But for some reason > MySQLd uses 100% of my CPU with no queries happening. I tried to run > ktrace and this was all I saw: > > > 30488 mysqld CALL gettimeofday(0x2846e288,0) > 30488 mysqld RET gettimeofday 0 > 30488 mysqld CALL poll(0x83b6000,0xc,0) > 30488 mysqld RET poll 0 > 30488 mysqld CALL poll(0x83b6000,0xd,0x126) > 30488 mysqld RET poll 1 > 30488 mysqld CALL gettimeofday(0x2846e288,0) > 30488 mysqld RET gettimeofday 0 > 30488 mysqld CALL poll(0x83b6000,0xd,0x126) > 30488 mysqld RET poll 1 > > With an occasional > > 30488 mysqld CALL poll(0x83b6000,0xd,0x126) > 30488 mysqld PSIG SIGPROF caught handler=0x2842562c mask=0x0 > code=0x0 > 30488 mysqld RET poll 1 > 30488 mysqld CALL gettimeofday(0x2846e288,0) > 30488 mysqld RET gettimeofday 0 > 30488 mysqld CALL sigreturn(0x83a9db8) > 30488 mysqld RET sigreturn JUSTRETURN > > > Has anyone experienced a runway mysqld on FreeBSD before? Is there > anything I can do to fix this or solve this problem? Below is show > innodb status\g > > = > 030828 14:36:37 INNODB MONITOR OUTPUT > = > Per second averages calculated from the last 16 seconds > -- > SEMAPHORES > -- > OS WAIT ARRAY INFO: reservation count 4, signal count 4 > Mutex spin waits 0, rounds 0, OS waits 0 > RW-shared spins 6, OS waits 3; RW-excl spins 1, OS waits 1 > > TRANSACTIONS > > Trx id counter 0 1280 > Purge done for trx's n:o < 0 0 undo n:o < 0 0 > Total number of lock structs in row lock hash table 0 > LIST OF TRANSACTIONS FOR EACH SESSION: > ---TRANSACTION 0 0, not started, OS thread id 299134976 > MySQL thread id 176926, query id 516226 localhost root > show innodb status > > FILE I/O > > I/O thread 0 state: waiting for i/o request (insert buffer thread) > I/O thread 1 state: waiting for i/o request (log thread) > I/O thread 2 state: waiting for i/o request (read thread) > I/O thread 3 state: waiting for i/o request (write thread) > Pending normal aio reads: 0, aio writes: 0, > ibuf aio reads: 0, log i/o's: 0, sync i/o's: 0 > Pending flushes (fsync) log: 0; buffer pool: 0 > 40 OS file reads, 4 OS file writes, 4 OS fsyncs > 0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s > - > INSERT BUFFER AND ADAPTIVE HASH INDEX > - > Ibuf for space 0: size 1, free list len 0, seg size 2, > 0 inserts, 0 merged recs, 0 merges > Hash table size 34679, used cells 0, node heap has 0 buffer(s) > 0.00 hash searches/s, 0.00 non-hash searches/s > --- > LOG > --- > Log sequence number 0 43892 > Log flushed up to 0 43892 > Last checkpoint at 0 43892 > 0 pending log writes, 0 pending chkp writes > 9 log i/o's done, 0.00 log i/o's/second > -- > BUFFER POOL AND MEMORY > -- > Total memory allocated 16338600; in additional pool allocated 641280 > Buffer pool size 512 > Free buffers 493 > Database pages 19 > Modified db pages 0 > Pending reads 0 > Pending writes: LRU 0, flush list 0, single page 0 > Pages read 19, created 0, written 0 > 0.00 reads/s, 0.00 creates/s, 0.00 writes/s > No buffer pool page gets since the last printout > -- > ROW OPERATIONS > -- > 0 queries inside InnoDB, 0 queries in queue > Main thread id 158370816, state: waiting for server activity > Number of rows inserted 0, updated 0, deleted 0, read 0 > 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s > > END OF INNODB MONITOR OUTPUT > > Nick > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/m
