I recently upgraded a customers server from a P3/XEON box to a 64-bit Opteron
with 16GB RAM. They have more data than can easily be handled by a 32-bit
machine with the inherent limit of ~2GB on innodb_buffer_pool and is now much
faster. The old server ran 4.0.18 and I upgraded to 4.0.20 on the
I've recently gotten an AMD Opteron 64-bit machine for MySQL testing and
eventual deployment. I have a web server with MySQL and 48 databases of roughly
36GB total, stored as INNODB. The current server is a dual Xeon 2.8Ghz machine
with 4GB RAM. Since it's 32-bit about 1.2GB is the highest I can
You don't mention CPU type but do mention RedHat 9. Is this on 32-bit x86
hardware or something 64-bit? How do you set innodb_buffer_pool_size to anything
2GB on a 32-bit box if it is? I've got it set to 7GB on a dual Opteron box
with 8GB RAM with great results so far (in testing, go live next
: Tuesday, August 26, 2003 4:08 PM
To: [EMAIL PROTECTED]
Subject: Re: 64-Bit and INNODB
Hi!
- Original Message -
From: Marc Slemko [EMAIL PROTECTED]
Newsgroups: mailing.database.mysql
Sent: Tuesday, August 26, 2003 6:56 AM
Subject: RE: 64-Bit and INNODB
On Mon, 25 Aug 2003, Wendell Dingus
MySQL is pretty good about following symlinks. Move /var/lib/mysql to
/mnt/ramdisk/mysql and then symlink to it.
# ln -s /mnt/ramdisk/mysql /var/lib/mysql
Changing where everything resides in my.cnf should have been sufficient
but the symlink way works great as well. And there should be no
You might also like the INNODB table type for which there is a fairly
large online manual at http://www.innodb.com/ibman.html
-Original Message-
From: Johnson, Michael [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 19, 2003 12:48 PM
To: 'Andy Jackman'
Cc: MySQL Users
Subject: RE:
I just want to be 100% sure on something...
With an Opteron (or Itanium for that matter) using let's say the RedHat 9 or
AS 3 betas available for those CPUs, how will MySQL/INNODB function?
Specifically does the ability to allocate a bigger chunk of memory than 2GB
just work out of the box? Can I
Quoting Jackson Miller [EMAIL PROTECTED]:
I need to migrate a 3.23.52 MySQL server to a version with InnoDB (and row
level locking). The catch is, I need to do it in a hurry (by the end of the
week). It is a production system with over 300 users. Some tables have over
2,000,000 rows.
I've been immersing myself in reading and trying to understand what I
can about how keys and indexes work and the flow of a query. Here's an
example of one that's not real efficient and I'm not sure if it can be
made any more efficient or done some other way to go faster though. I'm
guessing a
I think I know the answer to this question, but.. Just to be sure.
Can I take multiple 2GB files in /var/lib/innodb and the corresponding
files in /var/lib/iblogs created with 3.32.55 (INNODB) and upgrade to
4.0.13 and let it use those existing files without a problem? Without
dumping and
If your internet connections aren't very fast and stable, or perhaps
dialup or similar you can do a poor-mans replication. I do this and
after lots of starts and stops on my scripts that get the data to the
slave server it's finally working very good. When you turn on bin-log in
my.cnf it just
Thanks to everyone who has helped and/or made suggestions so far. I'll
try to provide some answers to your further queries and report back on
some testing I've done.
Jeremy asked for explains of some of the problem queries:
Here is a particularly troublesome one that gets ran quite a lot:
mysql
Hello, I've got a situation I'm hoping someone here can help me out with. We
have a web server serving up data via some PHP programs pulling from MySQL
(3.23.56 currently) in INNODB tables. There are 40+ (active) databases
totalling a bit over 28 Gigabytes at this point. As we add more users speed
: Joseph Bueno [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 28, 2003 2:45 PM
To: Wendell Dingus
Cc: [EMAIL PROTECTED]
Subject: Re: MySQL/INNODB speed on large databases
Maybe my question is too obvious but, since you have several databases
instead of only one, have you considered moving some of them
Is the inability for 4.0.12 (and previous) SRC RPMs to build on RedHat 8 the
fault of something in MySQL or RedHat? Is there any plans to resolve this any
time soon?
Thanks!
-
This mail sent through IMP: http://horde.org/imp/
It doesn't appear to build. This is on a RedHat 8 machine with all
current patches applied from RedHat and kernel 2.4.18-19.8.0 Any
ideas?
# rpmbuild -bb --target i686 mysql-4.0.9-gamma.spec
(snip)
rm -rf .libs _libs
rm -f *.lo
rm -f Makefile bdb/Makefile stamp-h stamp-h[0-9]*
rm -f config.h
In 3.23.x versions of MySQL the actual binary log file sizes stayed
fairly consistent. An 'empty' log file for instance on 3.23.53a is 73
bytes. I have a situation where I'm doing a roll-your-own replication
from many sites to one central server where the remote sites are on
everything from dialup
I've got a Linux server (RH 7.3, 2.4.18, 1.5GB RAM) which runs good but
could always be faster. Memory is relatively cheap all things considered, so
we just added 4GB to it. I can increase innodb_buffer_pool_size from the
800M I had it at previously only to about 1500M without problems. I was
I've been using MyISAM tables for a long time on a lot of machines and
(knock on wood) have basically never had a problem. Now though on a larger
server I decided we should use INNODB tables and am having problems. I
didn't realize until today that it's been 'crashing' and recovering
repeatedly
except for the
table changes though...
Anyway, thanks and hopefully this info can help you or whomever on the
development team to track this down.
-Original Message-
From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 22, 2002 1:37 AM
To: Wendell Dingus
Cc: [EMAIL
a
field to a table or similar do not.
Thanks...
-Original Message-
From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 16, 2002 9:23 PM
To: Wendell Dingus
Cc: [EMAIL PROTECTED]
Subject: Re: Bug in replication 3.23.46-max
On Tue, Jan 15, 2002 at 10:59:07PM -0500
I'm fairly certain this is a bug. It's on 3.23.46-max and the changelog for
.47 doesn't mention it.
I have 2 servers using replication. Server1 is used by client machines and
all updates are to it. Server2 stays in perfect sync with it and logs all
updates to it's own binary log. I then use
I've been using mysqlbinlog to capture a file of inserts/updates/deletes on
numerous servers since the early 3.23.x days. I have 3.23.46-max on a pair
of servers now though where it is exhibiting some strange behavior. Based on
some emailed suggestions I've tried leaving off the -uroot -ppassword
Version 3.23.46-max on a dual Xeon RedHat 7.2 machine with all RedHat
patches and their latest -smp kernel.
I turned on binary logging on a particular database with binlog-do-db= and
later try this:
mysqlbinlog -uroot -pxxxyyy binlogfilename-bin.001
It shows me the inserts and deletes that
I've searched the lists, newsgroups, etc... The info that's out there is
somewhat confusing or not as complete as it should be. This is a bit more of
a Linux question than a MySQL one but folks on here are likely to be the
ones to know the answer.
Can anyone give a suggestion as to the best way
This is on a RedHat 7.1 (very recently freshly installed) server with all
patched from updates.redhat.com installed and kernel 2.4.3-12. RedHat 7.1
installed MySQL 3.23.36 and that's what it was running until this problem
came up and I upgraded it to 3.23.40 from the Roswell beta directory from
I haven't read through any of the MySQL mailing lists in a while. Now that I
do I see that lots of the AIX related questions involve problems with
/usr/local/lib/libz.a as part of the ZLib compression library. The
pre-compiled ZLib on http://www.bull.de/pub/ fails for me with the [shr.o]
missing
27 matches
Mail list logo
