What part of fetching is taking them most time? Reading from the DB? Creating POJO-Classes? Sending data? Profile your code, find out which part of it needs to be tweaked. But using some kind of paging, as gregor mentioned is good in any case.
On 5 Nov., 15:56, gregor <[EMAIL PROTECTED]> wrote: > Hi, > > The short answer is don't fetch even 500 records in one go from the > server - you should use a paging table of some sort. e.g. > > http://code.google.com/p/google-web-toolkit-incubator/wiki/PagingScro... > > regards > gregor > > On Nov 5, 6:54 am, livinglegends <[EMAIL PROTECTED]> wrote: > > > Hi to All, > > > I am newbie to this group. I have one critical issue. Please help me > > regarding this. > > > I have some performance related issue with GWT-RPC. > > > I have create one method on server side which will fetch data from > > database, create one POJO class for one record, store all POJO classes > > in > > ArrayList and return that ArrayList object. > > > Problem is, when there will be less records say 10-30, I will get > > response > > from server to client in acceptable time, but if there will be more > > records > > say 500+, it will taking to much time say more than 5 minutes to > > return > > ArrayList of POJO classes(500+). > > > How can I improve performance because in future there might be 5000+ > > records which I need in one response from server. Please give me > > suggestion > > and if possible solution for this issue as I stuck with this issue > > since > > long but not able to get rid of this issue. > > > thanks in advance. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
