Be very careful about the judgements you make regarding performance based upon random data. Unless you are reasonably sure that your data will truly be random, you might get better results with algorithms that exploit the tendancy for real data not to be random."
I am definitely mindful of that. There's always a purpose. Actually I tested a large number of known sorting algorithms, so I could probably tell you which one would ideally work in each purpose. The only one for COBOL programs that's ideal seems to be combsort, but that's not a great algorithm for languages that can handle index processing better than COBOL can.
"Glenn, tell us about your results..."
There's not much for results right now, because it's an apples to oranges comparison (my typed sort versus untyped sorts). But I did get a great idea of where some possible performance lines are so I can see how I will do with my sort when it is written to be an untyped one (my sort routine is kind of in beta stage).
As far as the program you provided me goes, it refused to sort my full testbed file (20m records, 80MB is evidently too much for it so it returned an error), but I pared the file down to 5m records and it worked. As far as time goes with the 5m records, my program has about 14 seconds to play with. Like I said though, a typed sort isn't good to compare against an untyped one, but at least it gives me a good idea of where my code is at performance-wise for now.