Unfortunately, there's not really a "IO priority" setting. It's largely
first come, first serve.
It think one of the best ways to do this would be to space out the IO over
time, putting in a hard Sleep time. Then try do the IO in good-sized chunks.
This is much better than a lot of very small IO operations and there are
several reasons for that.
First of all, if you're competing with other apps, or the swap file, or the
user doing other stuff with the disk, doing the IO operations in chunks will
minimize how much the disk heads have to hop back and forth between the
indexing and whatever else is competing with it.
More importantly, if you're writing, and other apps are writing, if you do a
lot of small writes, you'll end up with more fragmentation, as the OS is
likely to do a bit of your file, followed by a bit of competing app file,
followed by a bit of your file, and so on. Writing in sizable chunks, you'll
end up with less disk fragmentation and better overall performance.
Anyway, that's just my opinion.
Pete