Project

General

Profile

Forums » Open discussion »

wiki - memory usage actual numbers, performance numbers?

Added by darren hartford about 14 years ago

Hey all,

I've been reading up about Wt, and it sounds very intriguing. However, one of the challenges I have in evaluating new language is having real/actual numbers based on simple/moderate/complex style examples.

'low memory' is nice, but what does that represent? I can not seem to find in the public website or the community wiki actual footprint sizes for various types of applications and/or other performance metrics.

Thanks in advance, and although getting numbers myself might seem like an easy answer, when you look at the close to 100 other alternatives, someone isn't going to make an example for each alternative ;-)

-D


Replies (4)

RE: wiki - memory usage actual numbers, performance numbers? - Added by darren hartford about 14 years ago

Thanks Wim,

I guess I was looking for more real-world numbers (more than one screen). One user put in a post about 1000-someodd screen/operations taking around 300mb, and although that might be extreme in some cases, with some other footprint numbers people can gauge where there application might fall into with Wt.

-D

RE: wiki - memory usage actual numbers, performance numbers? - Added by Koen Deforche about 14 years ago

Hey Darren,

Memory used by Wt depends only on the number of widgets currently created. If memory usage is a concern, you can always chose to not create widgets that aren't displayed --- so the memory usage of a single screen is really a good metric of how much memory Wt needs at a minimum (without taking into account possible optimations such as view-only widgets (WViewWidget), regardless of application complexity.

Regards,

koen

RE: wiki - memory usage actual numbers, performance numbers? - Added by darren hartford about 14 years ago

I understand there are caveats with measuring memory, but having someone looking to, for example, port an ASP.NET web application, a JavaEE (JPA and/or JSP and/or JSF and/or GWT and/or echo) web application, a tomcat (hibernate and/or ibatis and/or struts and ) into a similar application in Wt.

Example (not real, just GUESSES) for Ram on x86 Ubuntu intel/amd:

Wt: Hello world: 400k base, 1.5k per user session

Wt: 20 screen app (simple) with 40 dataretrievals and 20 update (2/1 per screen): 800k base, 3k per user session

Wt: 100 screen app with complex/composite/multi-tier/tree views with 500 datacalls and 180 update on average per screen: 10MB base, 5k per user session

While someone might have already written a similar application in their existing technology (lets two out of the three are 50MB base, 1mb per session, while JavaEE will depend on the container selected). It becomes easier to see how Wt may benefit users who already have the right skillset, or balance if it is worthwhile to learn the new skillset.

But...without some actual numbers, hard to justify if it would be worthwhile or not :-)

-D

    (1-4/4)