In response to Jennifer Trey <jennifer.trey@gmail.com>:
> Hmm, I just noticed the same write behavior on my Windows Xp laptop but the
> values was a little less.
> I even created an DB with one table and column and this still happened
> when querying it.
By "created", you mean you created a table and populated it with data?
Once you do that, do a "SELECT count(*)" on that table, then wait for
the I/O to calm down. That select statement will force all the hint
bits to be updated. See if subsequent selects still cause disk
activity.
> Are you sure that moving to Linux will solve this?
I never advocated that Linux would fix this, and I still don't. I
recommended a short list of methods to investigate the issue, most of
which you ignored. You _still_ don't know what's being written, and
I _highly_ recommend that you isolate that before doing something
radical like switching operating systems.
If you've got the DB configured in such a way that it's causing a lot of
write ops, it's going to do it in Linux or any other Posix systems, or
on CP/M for that matter.
Posix systems have a laundry list of tools to identify what programs are
doing. It's been a while since I've worked with Windows, but I seem to
remember MS having tools to audit disk activity. Turn them on and see
which files are actually being written to.
> Could you please check if
> you notice the same write behavior?
My BSD-based systems to no do this. Doing a select count(*) on a table
with 750,000 rows produces no write activity.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/