Hi Pravin,
Seems that u r currently facing with 2 probs :-
1. Faster sorting model
2. Performance issues (i.e. even if u don't use Sorting it is taking time)
For prob.no. 2, take a look at the foll. link :-
http://developer.java.sun.com/developer/community/chat/JavaLive/2003/jl0121.html Actually prob.no. 1 and 2 can be solved if we write a custom MutableTreeNode that internally uses SortedSet for storing children.
Java's DefaultMutableTreeNode uses Vector as internal collection. The reason is that Vector and Hashtable were released (i think) with JDK1.1 and the Collection Framework was released with JDK1.2. Since Collection framework was not available during development of swing library they heavily used Vector and Hashtable. U can see the probs arises with JList, JComBox, JTable etc.. Needless to say Vector is very poor performance wise.
Recently we faced similar probs with JList. The list would have to be populated with millions of data. When we started with list's default Vector it was taking terrible time even for standalone version. We thought of providing progress bar. But later we wrote our custom SortedListModel (not a big stuff) but improved the performance so amazingly that now there was no need of progress bar and the millions of records were displayed within few sec. Note that this is a standalone application
Hope this helps