> The dataset I was sorting on was generated specifically to test the speed of > different comparators, and had a dataset of 100,000 elements, and I was > sorting using the standard sort method from the collections package, > accessed from Arrays.sort(). However, I now have data that times individual > calls of the Comparator's compare() method:
You would never load a data set of 100,000 elements (or even a 1,000 for that matter) in Wicket models, simply because you wouldn't display that many components (your browser probably wouldn't be able to handle that for instance). Furthermore, even if you would find the need to do such sorting in-memory using Java, you would do that upfront, before arriving at the user interface layer. Eelco
