|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-13 05:21:00
|
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
|