This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
We faced multiple issues when trying to display large amount of data for a screen. Some of them include.. 1) poor performance on the database side. 2) Screen rendering taking a lot of time. 3) If there is business logic to be executed on the data retrieved from the database you might face memory issues....etc
I am really not sure how it will be beneficial to display large amount of data on a single screen to the end user for your use case.
The better option is to implement some pagination logic which will show maller chunks of data and thereby eliminate any screen rendering ormemory related issues.
Another option is to use Ajax so that the client perception also improves.
In addition to above.. I would guess you don't want to display huge amount of data, you need to process it instead. If that's the case, just use jdbc preparedStatement and avoid creating objects for each loop (I think it's called flyweight pattern) and do the processing. Use scrollable ResultSet if there is a need for that. You can use more then one connection and process them in parrellel. Consider prefetching data. Hope it helps.