As my application grows in size, can anyone recommend a good way to analyse resource (I suppose this really means memory) usage from within the app?

I create and destroy forms all the time, and I *think* I'm doing it properly. But it would be good to know how others profile their EWB2 apps.

Petter Topp has just asked a question regarding modularisation (http://www.elevatesoft.com/forums?action=view&category=ewb&id=ewb_general&msg=7547&page=1) to which I will add my curiosity, and I think this compliments that question as my app is growing considerably as well.

squiffy wrote:

> from within the app?

That is the key here, and I suspect probably not. Using the Chrome
profiler you can see how you are doing, but I'm not aware of a way for
the application itself to know.

One daft thought is that I have implemented a system for some reason I
don't recall a way to have the page refresh itself completely, but also
to be able to log itself back in automatically by storing a one off
token in LocalStorage. Someone very concerned could do that once a day!

--

Matthew Jones

<< As my application grows in size, can anyone recommend a good way to analyse resource (I suppose this really means memory) usage from within the app? >>

Not from within the application, no.  But, you can do this in the Chrome developer tools (F12), as well as other browsers.  Chrome will show you memory usage over time, total memory usage, DOM element usage, etc.

However, remember something very important: code size <> memory usage.  So, just because your application is getting large does *not* mean that it is necessarily consuming a lot of memory.

Tim Young
Elevate Software
www.elevatesoft.com