Programming

Happy with it not being completely random, as long as it jumps around enough to not catch itself on the read advance routines when running on the SAN, and as simulation goes, the database would more than likely read specific files or parts of files more than others anyway.

Here comes my next exciting problem, a database will only read a certain amount of time, other bits are sorting, writing and whatever else the database gets up to. So I am thinking of adding how manny cycles there are between reads, because just doing random reads and nothing else is giving rather silly results. In its purest form I seem to be able to get 100% WaitI/O and read about 6-12 Kb/s, which is pretty impressive in its ow right.

And todays exiting question, anyone feel like guessing how many cycles in a million that a rather streamlined database spends reading disk data
Anyone who guesses the right answer wins an icecream, collectable in Camden, London (U.K.)

/Ben