Hi friends,
we're developing a new web application that works with a db around 1gb
and 30 tables.
We work with linux, and I'm evaluating the benefit of making an specific
partition (ext3) for mysql in order to have a bigger Block Size. Block
Size by default in / partition is 4096.
Do you think
Will you be using the MyISAM or InnoDB table engines?
I had heard that InnoDB uses 16k blocks internally, so that might be a good
starting point, though I'd love to have someone confirm or deny that this is
actually true.
-Aaron
On Fri, May 9, 2008 at 12:01 AM, Iñigo Medina García
[EMAIL
I would use as large a block size as you dare, especially with InnoDB.
Makes reading and writing faster as custs down seek time as cuts down
disk fragmenation and avoids block table reads. With MyIsam you have
lots of files, but if you only have a few again might work well with a
large
Upgrade to 5.0.51b seems to have solved the problem. On wednesday, I saw
the problem about a dozen times during a peak time. Upgraded wednesday
night and have not seen the error since.
Thanks
Dominik
Juan Eduardo Moreno wrote:
Hi,
This error occur when slave servers could incorrectly
Thanks, Aaron.
Will you be using the MyISAM or InnoDB table engines?
Both, but InnoDB more.
I had heard that InnoDB uses 16k blocks internally, so that might be
a good starting point, though I'd love to have someone confirm or deny
that this is actually true.
Ok, that's interesting. :-)
Thanks Ben.
I would use as large a block size as you dare, especially with InnoDB.
Makes reading and writing faster as custs down seek time as cuts down
disk fragmenation and avoids block table reads. With MyIsam you have
lots of files, but if you only have a few again might work well with
I'm seeing that architecture has almost allways the limit in 4 kb (block
size - page). Theoretically architecture of 64 bits would offer up to 8
kb, but it seems to be that it usually has 4 kb too because of
compatibiliry issues with its i386 ancestors.
Any idea about that? We run Intel Core 2
Will you be using the MyISAM or InnoDB table engines?
I had heard that InnoDB uses 16k blocks internally, so that might be a good
starting point, though I'd love to have someone confirm or deny that this is
actually true.
Yep, Aaron. Look at: http://www.innodb.com/innodb/features/
and
Dear MySql,
I am trying to optimise InnoDB, and trying to find out how much of the
innodb log file contains row data which has not been written to storage.
Therefore I can optimize the size of the log, keeping it low to reduce
crash recovery time yet high enough to be useful.
I can see
Hi Ben,
Dear MySql,
I am trying to optimise InnoDB, and trying to find out how much of the
innodb log file contains row data which has not been written to storage.
Therefore I can optimize the size of the log, keeping it low to reduce
crash recovery time yet high enough to be useful.
Thanks for the idea. Unfortunately nothing I can easily use (for
instance in MySql Administrator) to log and monitor the lag in bytes
between log writes and row data writes. :)
Iñigo Medina García wrote:
Hi Ben,
Dear MySql,
I am trying to optimise InnoDB, and trying to find out how
Hi,
How does one know if ON UPDATE CURRENT_TIMESTAMP was specified when
creating a column? How do I retrieve this bit of info from the metadata
queries?
(also MySQL 4.1)
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle
MS SQL Server
Upscene Productions
SHOW CREATE TABLE ...
Martijn Tonies wrote:
Hi,
How does one know if ON UPDATE CURRENT_TIMESTAMP was specified when
creating a column? How do I retrieve this bit of info from the metadata
queries?
(also MySQL 4.1)
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL,
SHOW CREATE TABLE ...
Yes, I thought so :-(
From a coding point of view, this requires parsing...
Why isn't there anything in show full columns.
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle
MS SQL Server
Upscene Productions
Hello,
I _thought_ I knew how InnoDB worked, but due to a recent mysql doc
change, I am no longer sure--the change made the dox significantly
less clear, and potentially code-breaking.
Please can someone tell me the real behavior of InnoDB in the
following case, and ideally clarify the dox
That's true in some workloads, but with InnoDB you'll usually run into data
file fragmentation before filesystem fragmentation (unless it's a shared
system). This is especially true if your application runs a lot of updates
or deletes as random chunks of space will become free at different points
Hey everyone,
I'm pretty sure this is right but I wanted to double-check:
Is it correct that mysql 5.0 is threaded in such a way that a DB server taking
lots of queries from many clients will be able to utilize lots of CPUs/core
on a multi-cpu, multi-core system?
Or are multi CPUs/cores a
Yes it can use multiple cores. Mysqld is a multithreaded service.
Saravanan
--- On Sat, 5/10/08, JW [EMAIL PROTECTED] wrote:
From: JW [EMAIL PROTECTED]
Subject: Best CPU config for a busy DB server
To: mysql@lists.mysql.com
Date: Saturday, May 10, 2008, 3:52 AM
Hey everyone,
I'm pretty
On Friday 09 May 2008 04:32:10 pm Saravanan wrote:
--- On Sat, 5/10/08, JW [EMAIL PROTECTED] wrote:
From: JW [EMAIL PROTECTED]
Is it correct that mysql 5.0 is threaded in such a way that
a DB server taking lots of queries from many clients will be able\
to utilize lots of CPUs/core on a
At 05:05 PM 5/9/2008, you wrote:
On Friday 09 May 2008 04:32:10 pm Saravanan wrote:
--- On Sat, 5/10/08, JW [EMAIL PROTECTED] wrote:
From: JW [EMAIL PROTECTED]
Is it correct that mysql 5.0 is threaded in such a way that
a DB server taking lots of queries from many clients will be able\
20 matches
Mail list logo
