Re: Real-time app: best approach

400mb? :-)  That would be a general design/implementation issue: not GWT specific.  Regardless of frameworks, there needs to be paged requests from UI to server and server to Db.  Play with request and cache sizes to get memory footprint -vs- performance balanced where you want.  Good luck!

On Fri, Dec 31, 2010 at 1:50 AM, remuera <brainbug@web.de> wrote:

Hello,

I've developed an app using GWT 2.1 and GXT 2.2.1 and having these
problems:

1) It is a real-time app (data update 4 times a second!) and I want to
update a grid/table with about 80 lines. The data is not that large,
some doubles and a string.

2) The user should be able to generate a report with a lot of data,
that should be displayed in a pure HTML table (up to 5000 rows). My
solution right now works not bad, but the memory usage is huge (around
400 MB!).

I would like to hear your recommendations on these two requirements.
How would you implement them? The app should be as performant as
possible with using GWT and GXT (if possible). I am deploying it on a
Tomcat 6.

Thank you in advance!

Tim

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.