> So the new question is now: what is in the code that hasn't 
> been shown?

One other possibility is that he was running on a machine that was short of
real memory, and the job was thrashing the disk. That's one possibility I
wanted to eliminate by asking how it scales.

Michael Kay
http://www.saxonica.com/