Home » Eclipse Projects » Remote Application Platform (RAP) » Browser Memory Usage
| Browser Memory Usage [message #100372] |
Mon, 28 July 2008 16:13  |
 laurent delvaux
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
Hi,
First of all I would like to congratulate the RAP team for their job : RAP
is very impressive and seems very robust!
Nevertheless, I have recently notice that it looks quite "browser memory"
consuming.
To illustrate this "problem", let's consider the RMS Online Demo
(http://rap.eclipse.org/rapdemo/rms).
Step 1 : double click on "Product 1", "Product 2" and "Product 3"
contained in "Principal 6" to open 3 editors
Step 2 : then close the 3 editor tabs (P1, P2, P3)
Step 3 : iterate over "Step 1" and "Step 2" 4 more times (to play the
complete scenario 5 times)
Here are the results on different OS and browsers :
- Mac OS 10.5.4 / Safari 3.1.2 : start=40 MB -> end=51 MB => 11 MB
- Mac OS 10.5.4 / Firefox 3.0.1 : start=53 MB -> end=63 MB => 10 MB
- Win XP SP2 / Firefox 3.0.1 : start = 44 MB -> end=56 MB => 12MB
- Win XP SP2 / IE 6.0 : start = 64 MB -> end=109 MB => 45 MB
- Win XP SP2 / IE 7.0 : start = 69 -> end=116 MB => 47 MB
- I don't have any IE8 installed
First of all, under IE6, the application becomes quite unusable as the
test goes : it was very slow and produce a very bad user experience from
my point of view. It is not a big surprise because IE6 is known as a bad
Ajax application execution platform. Nevertheless, it means that for now
RAP is not a good solution to address IE6 populations. Do you share this
opinion ?
Despite I know that "JavaScript" garbage collection is completely
different from "Java" garbage collector, I'm surprised to get a such
memory consuming (from 10MB to more than 47MB). Is that normal?
I found a thread talking about such problems :
http://dev.eclipse.org/newslists/news.eclipse.technology.rap /msg02656.html.
Can you tell me if this memory usage 'll be improved by the Qooxdoo 0.8
integration and your client side widget pooling mechanism ?
Laurent
|
|
| |
| Re: Browser Memory Usage [message #100587 is a reply to message #100372] |
Tue, 29 July 2008 08:54  |
Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
qooxdoo works on IE 6. But as you've already encountered, if you're
running a non trivial sized app it is slow - very slow. But this is case
with all non trivial rich internet applications on IE 6, nevertheless
which javascript library is used. The root cause of this is the browser
itself, which is outdated. Microsoft forced the automatic update to IE 7
already on Feb. 12 via WSUS (Windows Server Update Services). So there
isn't much we can do about this.
In general the memory consumption is quite impressive but this seems
common to all javascript frameworks. The pooling mechanism should reduce
this cosumption be reusing existing but unused widgets.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Laurent Delvaux [mailto:laurent.delvaux@zenika.com]
Bereitgestellt: Montag, 28. Juli 2008 18:13
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Browser Memory Usage
Betreff: Browser Memory Usage
Hi,
First of all I would like to congratulate the RAP team for their job :
RAP
is very impressive and seems very robust!
Nevertheless, I have recently notice that it looks quite "browser
memory"
consuming.
To illustrate this "problem", let's consider the RMS Online Demo
(http://rap.eclipse.org/rapdemo/rms).
Step 1 : double click on "Product 1", "Product 2" and "Product 3"
contained in "Principal 6" to open 3 editors
Step 2 : then close the 3 editor tabs (P1, P2, P3)
Step 3 : iterate over "Step 1" and "Step 2" 4 more times (to play the
complete scenario 5 times)
Here are the results on different OS and browsers :
- Mac OS 10.5.4 / Safari 3.1.2 : start=40 MB -> end=51 MB => 11 MB
- Mac OS 10.5.4 / Firefox 3.0.1 : start=53 MB -> end=63 MB => 10 MB
- Win XP SP2 / Firefox 3.0.1 : start = 44 MB -> end=56 MB => 12MB
- Win XP SP2 / IE 6.0 : start = 64 MB -> end=109 MB => 45 MB
- Win XP SP2 / IE 7.0 : start = 69 -> end=116 MB => 47 MB
- I don't have any IE8 installed
First of all, under IE6, the application becomes quite unusable as the
test goes : it was very slow and produce a very bad user experience from
my point of view. It is not a big surprise because IE6 is known as a bad
Ajax application execution platform. Nevertheless, it means that for now
RAP is not a good solution to address IE6 populations. Do you share this
opinion ?
Despite I know that "JavaScript" garbage collection is completely
different from "Java" garbage collector, I'm surprised to get a such
memory consuming (from 10MB to more than 47MB). Is that normal?
I found a thread talking about such problems :
http://dev.eclipse.org/newslists/news.eclipse.technology.rap /msg02656.ht
ml.
Can you tell me if this memory usage 'll be improved by the Qooxdoo 0.8
integration and your client side widget pooling mechanism ?
Laurent
|
|
| |
| Re: Browser Memory Usage [message #100900 is a reply to message #100886] |
Wed, 30 July 2008 13:39 |
Stefan 
Messages: 316
Registered: July 2009 |
Senior Member |
|
|
Hi Stefan,
afaik, the widget pooling is currently disabled because the
qooxdoo-widgets are not "ready" to be re-used (JS-errors ocurred). Last
what I heard is that there are plans to reanimate the pooling mechanism
with qx 0.8.
One goal of client-side pooling is to lessen the effect of JS memory
leaks, especially with IE.
Frank, please correct me, if I said something wrong :-)
Regards,
Stefan.
stefan.hansel@tolina.de schrieb:
>
> Frank,
>
> do I see it right, that widget pooling has been disabled in RAP 1.1 (due
> to different problems ?)
> When do you think that it will be activated again ?
>
> Will widget pooling help applications, that often create and discard
> composites ?
|
|
|
| Re: Browser Memory Usage [message #101268 is a reply to message #100900] |
Tue, 05 August 2008 15:45 |
Markus Kohler
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Hi all,
See my comments below ...
Stefan Roeck wrote:
> Hi Stefan,
> afaik, the widget pooling is currently disabled because the
> qooxdoo-widgets are not "ready" to be re-used (JS-errors ocurred). Last
> what I heard is that there are plans to reanimate the pooling mechanism
> with qx 0.8.
> One goal of client-side pooling is to lessen the effect of JS memory
> leaks, especially with IE.
Regarding memory leaks. It is known that IE currently gets slower the more
memory the application uses.
It's is also well known that IE (even 7.0) has memory leaks and it's
therefore crucial for good "rendering" performance to avoid them.
Has anyone looked whether there are any memory leaks with qdox/RAP ?
I know that Microsoft has a tool to detect most of the leaks, but I'm not
sure whether that is available for the general public.
Regards,
Markus
> Frank, please correct me, if I said something wrong :-)
> Regards,
> Stefan.
> stefan.hansel@tolina.de schrieb:
>>
>> Frank,
>>
>> do I see it right, that widget pooling has been disabled in RAP 1.1 (due
>> to different problems ?)
>> When do you think that it will be activated again ?
>>
>> Will widget pooling help applications, that often create and discard
>> composites ?
|
|
| | | |
Goto Forum:
Current Time: Fri Apr 19 02:35:31 GMT 2024
Powered by FUDForum. Page generated in 0.02006 seconds |
] 
Search
Help
Register
Login
Home
