Hopbot log for 2009-10-07 - Helma IRC channel: #helma on irc.freenode.net

2009-10-07:

[10:10] <simono> hannesw, when i'm signed in @ google i see "web views" on this summary page http://groups.google.com/ .. last 16 hours 20 WV for NG
[10:10] <hannesw> simono: yeah, i saw that
[10:10] <hannesw> thx
[10:19] <zumbrunn> what about it?
[10:22] <hannesw> zumbrunn: talked with simono about my lack of updates on helma ng mailing list ... :)
[10:22] <hannesw> I updated the NG demo app
[10:22] <hannesw> removed continuations (which aren't continuations anymore really
[10:23] <hannesw> and added file upload, jsdoc, and unit testing demos :-)
[10:23] <hannesw> http://helma-ng.appspot.com/
[10:26] <simono> nice, apidoc already helpfull http://helma-ng.appspot.com/jsdoc/file
[10:27] <hannesw> simono: what do you mean?
[10:29] <simono> having automatic apidoc is nice and makes NG stand apart
[10:29] <hannesw> yep. but that link you posted throws an exception (the .js is missing)
[10:30] <hannesw> so I thought there were some irony tags there or whatever :)
[10:30] <simono> oops, not my intent
[10:30] <simono> test 1 2 http://helma-ng.appspot.com/jsdoc/helma/file.js/
[10:31] <simono> copypasta fail :)
[10:31] <hannesw> isee
[10:32] <hannesw> yes, some module's docs look good already.
[10:32] <hannesw> others have completely wrong names with their docs, or are just empty :)
[10:37] <simono> yeah, but in general.. with rhino's AST introspect abilities this is way ahead
[22:03] <mindlike> what is the memory footprint of helma 1.6x and ng on windows and linux by default?
[22:22] <earl> mindlike: just give it a try
[22:23] <earl> but the memory-lust of your jvm is typically a major factor
[22:25] <mindlike> in windows seems to start out using in the 40mb range plus the jvm using 100mb
[22:26] <earl> in my linux x32 apps i currently have ~120MB resident and ~400MB virtual (helma + jvm)
[22:28] <earl> (helma 1.x)
[22:29] <earl> for helma-ng on linux x64 i'm getting 55MB res for the demo app (and 1.2GB virtual, not that this matters much wich x64)
[22:49] <mindlike> the virt is a param in the helma conf no?
[22:54] <earl> nope, not really
[22:55] <earl> virt is the total amount of memory the process is using, wether it is paged out or resident in real RAM
[22:55] <earl> you can limit the maximum amount of memory a jvm allocates with -Xmx
[22:56] <earl> and this can be passed in the helma conf as well, yes
[23:01] <mindlike> any idea how the porting of modules to -ng is coming?
[23:01] <earl> do you have any specific module in mind?
[23:05] <mindlike> torrent, ssh
[23:29] <earl> mindlike: nope, no idea. will probably take some time unless someone volunteers and does it, or at least claims to desperately need them :)
[23:31] <mindlike> so basically the ng footprint is ~half the size of the native orig ver
[23:32] <earl> i'm not sure if this would be a fair comparison
[23:33] <earl> (at least not if you infer that from the numbers i gave)
[23:34] <earl> hng for example currently does not include any database connector libs
[23:34] <earl> whereas helma 1.x typically has some jars for connecting to mysql/postgres/etc
[23:35] <mindlike> yeah i was just looking for skeletal comps
[23:35] <mindlike> but good point
[23:36] <mindlike> mainly trying to determine if it could be offered as a low-cost (resource) browser/client conversion framework
[23:36] <mindlike> like enable server.. helma installs/starts.. what is system/resource cost to consumer/client
[23:37] <mindlike> compared to avg desktop apps/flash etc
[23:37] <earl> well, typically jvm's are considered to be rather resource-heavy
[23:37] <earl> but that depends a lot on what you're comparing it to, i guess
[23:37] <mindlike> yeah so when i run vuze i'm taxing it
[23:38] <earl> well, once you've got one jvm running, any further jvm's quickly "amortize" the costs
[23:39] <earl> both in startup time and in memory usage
[23:53] <mindlike> so the residential memory is jvm + helma?
[23:54] <mindlike> i guess it doesn't seem that heavy to average machine that can semi dedicate resources.. can you dynamically control system resource limits it uses as it runs or it needs to restart each time you adjust?

 

 

In the channel now:

Logs by date: