On 24.10.2006, at 20:09, Martin Cordova wrote:
Hello:
I am reading latest MaxDB online docs, and found this:
1) USE_OPEN_DIRECT
Q: do you recommend this on a Linux w/kernel 2.6? which Filesystems
make sense for this parameter?
I/O performance depends on a lot of parameters: controller, caches,
workload, filesystem, number and type of disks ....
There are configuration which will benefit from a bypassed filesystem
buffer cache - others won't :-(
Our advice is to run your own application benchmark to tune your local
configuration to an optimum.
2) "Only for UNIX/Linux: do not use hard disks with a journal file
system for the volumes. Journal file systems perform their own logging
of data changes, which is unnecessary for the database system and
leads to performance reduction."
Q: I am not familair with raw devices, so I was using XFS, because I
did read it was suitable for large files, like the ones I use with
MaxDB. The paragraph above put me think again... If I am not using Raw
devices, does this mean that I should use Ext2?? what about server
restarts? who will protect the integrity of my log and data files?
journaled filesystems (try to) prevent a loss of files, mixed up
permissions
and counters after a system crash. As we don't create or resize files
after the database setup, the database has no benefit from
using a journaled filesystem.
I would appreciate very much your comments on these topics.
- keep log and data on seperate disks
- use multiple (at least 3) data volumes of the same size.
- Increase the CACHE_SIZE within the physical memory size to reduce I/O
Henrik
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
