Re: [plexil-support] Memory issue

[Catherine S. <Cat...@ti...>]

There are 93264 lines total in all 71 plx files.

From: Catherine Szeto
Sent: Thursday, March 13, 2014 10:22 AM
To: 'Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)]'
Cc: ple...@li...; Scott Hetherington; Mark Guerra
Subject: RE: [plexil-support] Memory issue

Mike,
         There are 32 plans to be loaded directly with Main.ple, though if you include the plans that those 32 plans call, there are 71 plans in total. The total number of nodes for all 72 plx files is 3249. I'm working on getting the total number of lines for the plx files, but for a ballpark, the average plx has about 3000 lines, with a handful of small ones at around 500 lines.
         The memory size increases monotonically as Main.ple is trying to load. This takes about 2 min to load, and about 6 min before the giant while loop in Main.ple iterates quickly. Once Main.ple is up and running, the memory usage stays about the same.

Catherine

From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...]
Sent: Thursday, March 13, 2014 12:21 AM
To: Catherine Szeto
Cc: ple...@li...<mailto:ple...@li...>
Subject: Re: [plexil-support] Memory issue

Catherine,

3.5 GB does sound excessive.  Some questions...

Can you provide some quantitative information about the plans: total number of nodes (<Node> elements in the .plx files), total number of lines of the .plx files?

Can you characterize the memory usage?  Does plexilexec occupy 3.5 GB upon loading the Main plan (which effectively loads all the library plans)?  Or after running for a while?  Does memory size increase monotonically?

No suggestions offhand for reducing the memory footprint, but I'll talk about this with others, and  the information above will help.   I don't think the Plexil Viewer or the related startup options are an issue.

Mike


On Mar 12, 2014, at 8:14 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote:

Hello,
                We have a Main plan that will eventually have 32 plans with LibraryAction dependencies. We tried running the plan through the plexilexec with 25 of these dependent plans integrated. The plexilexec is using about 3.5 GB of memory, which seems excessive. We have several more plans to go that will be fairly large, so this is going to be a growing problem. Is there anything we can do to better manage the memory being used by the plexilexec to make the memory use more reasonable?

Thanks,
Catherine
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech_______________________________________________
plexil-support mailing list
ple...@li...<mailto:ple...@li...>
https://lists.sourceforge.net/lists/listinfo/plexil-support