On Wed, Sep 19, 2001 at 09:37:29AM -0700, Cameron Watters -- List Subscriptions wrote:
> Just a quick question regarding how (if at all) MySQL's binary update log
> consumes resrouces as it records modifications to various tables in the
> database.
>
> Are there any potential performance issues or limitations to be
> expected (other than excessive consumption of diskspace) if this log is
> not flushed/rotated periodically? Assuming diskspace isn't an issue what
> is the performance (RAM, CPU Usage) downside to not flushing this
> regularly?
There really isn't any downside (from a performance standpoint) in not
flushing it once in a while. The only real "work" for the server is
in either (1) deciding if a query belongs in the log, and (2) logging
it. Other than that, it's just appending to an ever-growing file.
As long as your OS can handle big files, MySQL really won't care.
Jeremy
--
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
MySQL 3.23.41-max: up 14 days, processed 259,839,665 queries (212/sec. avg)
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
