What kinda memory problems are you having? 30,000 rows and 80 columns is 2.4 million cells which is going to be a lot of memory. Do you run out of memory anytime you try to display that many things? Or do you run out of memory after several operations or your program running for sometime?
The former being a problem of using to much memory. Where do you get the data from? Is it a database or file? I have successfully displayed 50,000 rows in a JTable before with good performance. I reduced a considerable amount of memory usage by collapsing duplicate uses of memory. When you read stuff out of a database or file you can get lots of objects that are value equivalent (.equals()), I collapsed those references by passing all my data through a HashMap. hashMapInstance.put( value, value ); Then retrieving it again with hashMap.get( value ); That way all my objects ended up collasping into one reference for .equals(). I reduced my memory usage by 60%. If you think there is a leak, the later, then you'll most definitely need a memory profiler. You can get a 30 day trial license of OptimizeIT that's fully functional. You won't be able to find all of them on your own. Memory profiler is a must tool for Java. Try this, get OptimizeIT. Run your program, and look at the instance graph. (The one with the counts of instances, and red bars). Put a filter in at the bottom of OptimizeIT so that it's just your classes (i.e. net.my.program.*). Now look at what the number one count of instances is. Is that more than you expect? Now exercise the program in a way to make some of those instances out of use, push the GC button, and look at that instance count again. Did it go down? If not, you got a leak. charlie __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing
