> with your source file and destination files (DB) on the same drive, your limitations are likely to be disk head rather than anything else
Yes, yes, but they aren't; same server does not mean same drive. Unless I had no other choice, I would never put a large DB on the same drive as the OS and application files. In fact, I've already explained my setup for this application.
I thought threads for this because I have plenty of processor remaining (I'm only hitting about 20%) and because it would specifically take advantage of being able to read from one device interface while writing to another.
radiantmatrix
require General::Disclaimer;
s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}
In reply to Re^2: Implementing a buffered read-and-insert algorithm
by radiantmatrix
in thread Implementing a buffered read-and-insert algorithm
by radiantmatrix
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |