Hi...
If we are to compare MySQL/binlog with Oracle's redo log, there are some known
differences. First of all, the (somewhat) equivalent structure in Oracle for
the MySQL's binary log is not the redo log the log writer is writing to. It
is the archived log. The function of those is also
- Original Message -
From: Chao Zhu zhuc...@gmail.com
One Q: Can mysql binlog use raw device on Linux?
Mmm, good question. Don't really know; but I'm not convinced you'll get huge
benefits from it, either. Modern filesystems tend to perform pretty close to
raw throughput.
From a
Hi,
For the actual question, I agree with the points Johan mentioned. MySQL, to
my knowledge, does not have an option to use raw devices for binary logs. Even
if it had it, it would not have the benefits Chao is seeking. There is indeed
a tradeoff between losing transactions and
Thanks Guys;
The reason I was seeking RAW/AIO, is mostly about non-blocking write;
Which i mean:
Even though single write is not faster on RAW, if it supports raw and
Asynch IO write, then MySQL can continue to submit write request to disk
without waiting for the previous write to complete,
Thanks Guys;
The reason I was seeking RAW/AIO, is mostly about non-blocking write;
Which i mean:
Even though single write is not faster on RAW, if it supports raw and
Asynch IO write, then MySQL can continue to submit write request to disk
without waiting for the previous write to complete,
Just my two cents.
That's why it is Oracle.
Oracle is (almost) an operating system,
with its advanced implementation of device/file system management,
up to a logical volume management just consider ASM for example.
MySQL is quite simpler.
May be Oracle gurus could bring some key benefit to
hi, Guys
One Q: Can mysql binlog use raw device on Linux? Can we use asynch IO for
binlog writing? sequential non-qio fsync is slowing our throughput...
Thx
--
Regards
Zhu Chao
