You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
(2) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(6) |
Feb
(28) |
Mar
(27) |
Apr
(28) |
May
|
Jun
(6) |
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(13) |
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(10) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-04-01 16:43:38
|
Chris,
If the TestExec (plexiltest) is the version of Plexil you want to use, you must script time values. See the example plans and scripts in plexil-3/examples/basic.
Best,
Mike
On Apr 1, 2014, at 9:03 AM, "Fry, Charles R. {Chuck} (ARC-TI)[Stinger Ghaffarian Technologies Inc.
(SGT Inc.)]" <chu...@na...<mailto:chu...@na...>>
wrote:
Are you running this on the TestExec (plexiltest command)? The time interface always returns zero on that implementation. If this is the case, use plexilexec instead.
-- Chuck
On Apr 1, 2014, at 8:15 AM, Chris LANGLEY <Chr...@md...<mailto:Chr...@md...>>
wrote:
Good morning,
I am a complete newcomer to PLEXIL, so please excuse me if this is problem is due solely to my ignorance.
It appears that Lookup(time, tolerance) always returns 0.
I am using plexil-3 on Ubuntu 12.04.
The test program is a modification of plexil-3/examples/temporal/TimedIterationTest.ple
[Note that similar results were found using plexil 2.5 both precompiled and rebuilt, using timed-iteration.ple]
Code snippet below:
TimedIterationTest:
{
// variables snipped here
foo = TimedIterationTest.EXECUTING.START;
pprint("Start time = ", foo);
foo = Lookup(time, timeTolerance);
pprint("Lookup time = ", foo);
startTime = TimedIterationTest.EXECUTING.START + initialWait;
pprint("Run to start at", startTime);
// If either the "Start" or "EndCondition" lines below are uncommented, I do not get any printouts
// past this point – not even “Iteration completed at”
Iterate:
{
//Start Lookup(time, timeTolerance) >= startTime;
RepeatCondition i < repeatCount;
//EndCondition Lookup(time, timeTolerance) >= Iterate.EXECUTING.START + iterationInterval;
i = i + 1;
pprint("Iteration", i, "at", Iterate.EXECUTING.START);
pprint("Lookup ", i, "at", Lookup(time, timeTolerance));
}
pprint("Iteration completed at", Iterate.EXECUTING.END);
}
To compile this, I’m using:
plexilc TimedIterationTest.ple
To run this, I’m using:
plexiltest –plan TimedIterationTest.plx
When I run, I get:
No simulation script specified; using empty script.
Running executive from /home/ugps/plexil-3
Plan: TimedIterationTest.plx
Script: /home/ugps/plexil-3/examples/empty.psx
Libraries:
Library directories:
PORT:
Start time = 0
Lookup time = 0
Run to start at 10
Iteration 1 at 0
Lookup 1 at 0
Iteration 2 at 0
Lookup 2 at 0
Iteration 3 at 0
Lookup 3 at 0
Iteration 4 at 0
Lookup 4 at 0
Iteration 5 at 0
Lookup 5 at 0
Iteration 6 at 0
Lookup 6 at 0
Iteration 7 at 0
Lookup 7 at 0
Iteration 8 at 0
Lookup 8 at 0
Iteration 9 at 0
Lookup 9 at 0
Iteration 10 at 0
Lookup 10 at 0
Iteration completed at 0
If I uncomment the Start and EndCondition lines, I get:
No simulation script specified; using empty script.
Running executive from /home/ugps/plexil-3
Plan: TimedIterationTest.plx
Script: /home/ugps/plexil-3/examples/empty.psx
Libraries:
Library directories:
PORT:
Start time = 0
Lookup time = 0
Run to start at 10
And just to be sure, I set iterationCount = 100000 so that it would certainly go over 1 second of execution time. Still I get:
…
Iteration 99995 at 0
Lookup 99995 at 0
Iteration 99996 at 0
Lookup 99996 at 0
Iteration 99997 at 0
Lookup 99997 at 0
Iteration 99998 at 0
Lookup 99998 at 0
Iteration 99999 at 0
Lookup 99999 at 0
Iteration 100000 at 0
Lookup 100000 at 0
Iteration completed at 0
Any help would be greatly appreciated. Thanks.
Chris
Chris Langley, Ph.D., P.Eng.
Senior Engineer, Guidance, Navigation, and Control
MDA Space Missions
9445 Airport Road
Brampton, Ontario
CANADA L6S 4J3
1 (905) 790-2800 x4199
------------------------------------------------------------------------------
_______________________________________________
plexil-support mailing list
ple...@li...<mailto:ple...@li...>
https://lists.sourceforge.net/lists/listinfo/plexil-support
Chuck Fry
Senior Software Engineer
Dell | Services, Federal Government
Office: 650 604 1882 Mobile: 408 230 2715
M/S 269-1, Building N269/260-7
NASA Ames Research Center
Moffett Field, CA 94035-1000
I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me.
------------------------------------------------------------------------------
_______________________________________________
plexil-support mailing list
ple...@li...<mailto:ple...@li...>
https://lists.sourceforge.net/lists/listinfo/plexil-support
|
|
From: Fry, C. R. {C. (ARC-TI)[S. G. T. I. (S. Inc.)] <chu...@na...> - 2014-04-01 16:03:57
|
Are you running this on the TestExec (plexiltest command)? The time interface always returns zero on that implementation. If this is the case, use plexilexec instead.
-- Chuck
On Apr 1, 2014, at 8:15 AM, Chris LANGLEY <Chr...@md...<mailto:Chr...@md...>>
wrote:
Good morning,
I am a complete newcomer to PLEXIL, so please excuse me if this is problem is due solely to my ignorance.
It appears that Lookup(time, tolerance) always returns 0.
I am using plexil-3 on Ubuntu 12.04.
The test program is a modification of plexil-3/examples/temporal/TimedIterationTest.ple
[Note that similar results were found using plexil 2.5 both precompiled and rebuilt, using timed-iteration.ple]
Code snippet below:
TimedIterationTest:
{
// variables snipped here
foo = TimedIterationTest.EXECUTING.START;
pprint("Start time = ", foo);
foo = Lookup(time, timeTolerance);
pprint("Lookup time = ", foo);
startTime = TimedIterationTest.EXECUTING.START + initialWait;
pprint("Run to start at", startTime);
// If either the "Start" or "EndCondition" lines below are uncommented, I do not get any printouts
// past this point – not even “Iteration completed at”
Iterate:
{
//Start Lookup(time, timeTolerance) >= startTime;
RepeatCondition i < repeatCount;
//EndCondition Lookup(time, timeTolerance) >= Iterate.EXECUTING.START + iterationInterval;
i = i + 1;
pprint("Iteration", i, "at", Iterate.EXECUTING.START);
pprint("Lookup ", i, "at", Lookup(time, timeTolerance));
}
pprint("Iteration completed at", Iterate.EXECUTING.END);
}
To compile this, I’m using:
plexilc TimedIterationTest.ple
To run this, I’m using:
plexiltest –plan TimedIterationTest.plx
When I run, I get:
No simulation script specified; using empty script.
Running executive from /home/ugps/plexil-3
Plan: TimedIterationTest.plx
Script: /home/ugps/plexil-3/examples/empty.psx
Libraries:
Library directories:
PORT:
Start time = 0
Lookup time = 0
Run to start at 10
Iteration 1 at 0
Lookup 1 at 0
Iteration 2 at 0
Lookup 2 at 0
Iteration 3 at 0
Lookup 3 at 0
Iteration 4 at 0
Lookup 4 at 0
Iteration 5 at 0
Lookup 5 at 0
Iteration 6 at 0
Lookup 6 at 0
Iteration 7 at 0
Lookup 7 at 0
Iteration 8 at 0
Lookup 8 at 0
Iteration 9 at 0
Lookup 9 at 0
Iteration 10 at 0
Lookup 10 at 0
Iteration completed at 0
If I uncomment the Start and EndCondition lines, I get:
No simulation script specified; using empty script.
Running executive from /home/ugps/plexil-3
Plan: TimedIterationTest.plx
Script: /home/ugps/plexil-3/examples/empty.psx
Libraries:
Library directories:
PORT:
Start time = 0
Lookup time = 0
Run to start at 10
And just to be sure, I set iterationCount = 100000 so that it would certainly go over 1 second of execution time. Still I get:
…
Iteration 99995 at 0
Lookup 99995 at 0
Iteration 99996 at 0
Lookup 99996 at 0
Iteration 99997 at 0
Lookup 99997 at 0
Iteration 99998 at 0
Lookup 99998 at 0
Iteration 99999 at 0
Lookup 99999 at 0
Iteration 100000 at 0
Lookup 100000 at 0
Iteration completed at 0
Any help would be greatly appreciated. Thanks.
Chris
Chris Langley, Ph.D., P.Eng.
Senior Engineer, Guidance, Navigation, and Control
MDA Space Missions
9445 Airport Road
Brampton, Ontario
CANADA L6S 4J3
1 (905) 790-2800 x4199
------------------------------------------------------------------------------
_______________________________________________
plexil-support mailing list
ple...@li...<mailto:ple...@li...>
https://lists.sourceforge.net/lists/listinfo/plexil-support
Chuck Fry
Senior Software Engineer
Dell | Services, Federal Government
Office: 650 604 1882 Mobile: 408 230 2715
M/S 269-1, Building N269/260-7
NASA Ames Research Center
Moffett Field, CA 94035-1000
I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me.
|
|
From: Chris L. <Chr...@md...> - 2014-04-01 15:28:09
|
Good morning,
I am a complete newcomer to PLEXIL, so please excuse me if this is problem is due solely to my ignorance.
It appears that Lookup(time, tolerance) always returns 0.
I am using plexil-3 on Ubuntu 12.04.
The test program is a modification of plexil-3/examples/temporal/TimedIterationTest.ple
[Note that similar results were found using plexil 2.5 both precompiled and rebuilt, using timed-iteration.ple]
Code snippet below:
TimedIterationTest:
{
// variables snipped here
foo = TimedIterationTest.EXECUTING.START;
pprint("Start time = ", foo);
foo = Lookup(time, timeTolerance);
pprint("Lookup time = ", foo);
startTime = TimedIterationTest.EXECUTING.START + initialWait;
pprint("Run to start at", startTime);
// If either the "Start" or "EndCondition" lines below are uncommented, I do not get any printouts
// past this point - not even "Iteration completed at"
Iterate:
{
//Start Lookup(time, timeTolerance) >= startTime;
RepeatCondition i < repeatCount;
//EndCondition Lookup(time, timeTolerance) >= Iterate.EXECUTING.START + iterationInterval;
i = i + 1;
pprint("Iteration", i, "at", Iterate.EXECUTING.START);
pprint("Lookup ", i, "at", Lookup(time, timeTolerance));
}
pprint("Iteration completed at", Iterate.EXECUTING.END);
}
To compile this, I'm using:
plexilc TimedIterationTest.ple
To run this, I'm using:
plexiltest -plan TimedIterationTest.plx
When I run, I get:
No simulation script specified; using empty script.
Running executive from /home/ugps/plexil-3
Plan: TimedIterationTest.plx
Script: /home/ugps/plexil-3/examples/empty.psx
Libraries:
Library directories:
PORT:
Start time = 0
Lookup time = 0
Run to start at 10
Iteration 1 at 0
Lookup 1 at 0
Iteration 2 at 0
Lookup 2 at 0
Iteration 3 at 0
Lookup 3 at 0
Iteration 4 at 0
Lookup 4 at 0
Iteration 5 at 0
Lookup 5 at 0
Iteration 6 at 0
Lookup 6 at 0
Iteration 7 at 0
Lookup 7 at 0
Iteration 8 at 0
Lookup 8 at 0
Iteration 9 at 0
Lookup 9 at 0
Iteration 10 at 0
Lookup 10 at 0
Iteration completed at 0
If I uncomment the Start and EndCondition lines, I get:
No simulation script specified; using empty script.
Running executive from /home/ugps/plexil-3
Plan: TimedIterationTest.plx
Script: /home/ugps/plexil-3/examples/empty.psx
Libraries:
Library directories:
PORT:
Start time = 0
Lookup time = 0
Run to start at 10
And just to be sure, I set iterationCount = 100000 so that it would certainly go over 1 second of execution time. Still I get:
...
Iteration 99995 at 0
Lookup 99995 at 0
Iteration 99996 at 0
Lookup 99996 at 0
Iteration 99997 at 0
Lookup 99997 at 0
Iteration 99998 at 0
Lookup 99998 at 0
Iteration 99999 at 0
Lookup 99999 at 0
Iteration 100000 at 0
Lookup 100000 at 0
Iteration completed at 0
Any help would be greatly appreciated. Thanks.
Chris
Chris Langley, Ph.D., P.Eng.
Senior Engineer, Guidance, Navigation, and Control
MDA Space Missions
9445 Airport Road
Brampton, Ontario
CANADA L6S 4J3
1 (905) 790-2800 x4199
|
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-27 21:07:50
|
Catherine,
Unfortunately, Date is not actually a type in the Plexil exec. Dates and Durations are compiled into unit-less real numbers, which is all the exec knows about them.
You can process the printed real number with the 'date' command, something like
date --date="@secs"
where 'secs' is the printed integer (seconds since Unix epoch). Man 'date' for more information.
Mike
Hello,
How do I output time in the Date format? Here is what I tried:
Date Lookup time;
Date startTime;
pprint("startTime:", startTime);
I still got the startTime printed out as a Real number in the Unix time format.
Catherine
------------------------------------------------------------------------------
_______________________________________________
plexil-support mailing list
ple...@li...<mailto:ple...@li...>
https://lists.sourceforge.net/lists/listinfo/plexil-support
|
|
From: Catherine S. <Cat...@ti...> - 2014-03-27 19:25:08
|
Hello,
How do I output time in the Date format? Here is what I tried:
Date Lookup time;
Date startTime;
pprint("startTime:", startTime);
I still got the startTime printed out as a Real number in the Unix time format.
Catherine
|
|
From: Catherine S. <Cat...@ti...> - 2014-03-17 14:15:42
|
Thank you! We'll let you know how this goes. -----Original Message----- From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...] Sent: Friday, March 14, 2014 2:49 PM To: Catherine Szeto Cc: ple...@li...; Scott Hetherington; Mark Guerra Subject: PLEXIL-3 distribution A binary distribution built on 32-bit Ubuntu Linux 3.x is available here: https://sourceforge.net/projects/plexil/files/plexil/3.00/ Please see the README and CAVEATS files. In particular, note that $PLEXIL_HOME/scripts needs to be in your path, replacing $PLEXIL_HOME/bin. I *hope* this can simply "plug and play" with your existing application, but you'll have to see what happens! Let me know... Mike |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-14 19:49:14
|
A binary distribution built on 32-bit Ubuntu Linux 3.x is available here: https://sourceforge.net/projects/plexil/files/plexil/3.00/ Please see the README and CAVEATS files. In particular, note that $PLEXIL_HOME/scripts needs to be in your path, replacing $PLEXIL_HOME/bin. I *hope* this can simply "plug and play" with your existing application, but you'll have to see what happens! Let me know… Mike |
|
From: Mark G. <Mar...@ti...> - 2014-03-14 18:30:58
|
Thanks for replying.
________________________________________
From: Fry, Charles R. {Chuck} (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [chu...@na...]
Sent: Friday, March 14, 2014 1:04 PM
To: Mark Guerra
Cc: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)]; Catherine Szeto; ple...@li...; Scott Hetherington
Subject: Re: [plexil-support] Memory issue
I can answer that.
The plexil-3 branch was started as a platform for advanced development. Many internal and build system changes have been implemented and are being tested on internal applications at NASA Ames. At the same time, both Mike and I were assigned to work on these other applications, so the PLEXIL improvements were largely aimed at those projects, and we didn't have the time to spare to prepare the branch for release.
We do intend to release plexil-3, but we are hard at work on a near-term (as in, end of the month) spaceflight application at the moment.
-- Chuck
On Mar 14, 2014, at 3:14 AM, Mark Guerra <Mar...@ti...> wrote:
> Thanks for your help Mike.
>
> This is a curiousity question. Why has the development version of PLEXIL -3 not been released yet? Are there any plans to release it?
>
> Mark Guerra | Senior Software Architect |
> Tietronix Software Inc. | 1331 Gemini Ave. Suite 300 | Houston, TX 77058
> +1 (281) 404-7244 | mg...@ti... | www.tietronix.com
> ________________________________________
> From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...]
> Sent: Thursday, March 13, 2014 10:07 PM
> To: Catherine Szeto
> Cc: ple...@li...; Scott Hetherington; Mark Guerra
> Subject: Re: [plexil-support] Memory issue
>
> Thanks, and glad you sent that. I was starting to build on a (virtual) 64-bit version of that Ubuntu, but will get the 32-bit machine to match yours. Hope to have the distribution posted tomorrow.
>
> Mike
>
>
>> Ah, sorry. Here is what I get from that command:
>>
>> Linux ubuntu 3.2.0-60-generic-pae #91-Ubuntu SMP Wed Feb 19 04:14:56 UTC 2014 i686 i686 i386 GNU/Linux
>>
>> Thanks,
>> Catherine
>> ________________________________________
>> From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...]
>> Sent: Thursday, March 13, 2014 4:26 PM
>> To: Catherine Szeto
>> Cc: ple...@li...; Scott Hetherington; Mark Guerra
>> Subject: Re: [plexil-support] Memory issue
>>
>> PS: The output of 'uname -a' should suffice to answer my question about your Unbuntu version…
>>
>> Mike
>
>
> ------------------------------------------------------------------------------
> 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...
> https://lists.sourceforge.net/lists/listinfo/plexil-support
Chuck Fry
Senior Software Engineer
Dell | Services, Federal Government
Office: 650 604 1882 Mobile: 408 230 2715
M/S 269-1, Building N269/260-7
NASA Ames Research Center
Moffett Field, CA 94035-1000
I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me.
|
|
From: Fry, C. R. {C. (ARC-TI)[S. G. T. I. (S. Inc.)] <chu...@na...> - 2014-03-14 18:04:43
|
I can answer that. The plexil-3 branch was started as a platform for advanced development. Many internal and build system changes have been implemented and are being tested on internal applications at NASA Ames. At the same time, both Mike and I were assigned to work on these other applications, so the PLEXIL improvements were largely aimed at those projects, and we didn't have the time to spare to prepare the branch for release. We do intend to release plexil-3, but we are hard at work on a near-term (as in, end of the month) spaceflight application at the moment. -- Chuck On Mar 14, 2014, at 3:14 AM, Mark Guerra <Mar...@ti...> wrote: > Thanks for your help Mike. > > This is a curiousity question. Why has the development version of PLEXIL -3 not been released yet? Are there any plans to release it? > > Mark Guerra | Senior Software Architect | > Tietronix Software Inc. | 1331 Gemini Ave. Suite 300 | Houston, TX 77058 > +1 (281) 404-7244 | mg...@ti... | www.tietronix.com > ________________________________________ > From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...] > Sent: Thursday, March 13, 2014 10:07 PM > To: Catherine Szeto > Cc: ple...@li...; Scott Hetherington; Mark Guerra > Subject: Re: [plexil-support] Memory issue > > Thanks, and glad you sent that. I was starting to build on a (virtual) 64-bit version of that Ubuntu, but will get the 32-bit machine to match yours. Hope to have the distribution posted tomorrow. > > Mike > > >> Ah, sorry. Here is what I get from that command: >> >> Linux ubuntu 3.2.0-60-generic-pae #91-Ubuntu SMP Wed Feb 19 04:14:56 UTC 2014 i686 i686 i386 GNU/Linux >> >> Thanks, >> Catherine >> ________________________________________ >> From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...] >> Sent: Thursday, March 13, 2014 4:26 PM >> To: Catherine Szeto >> Cc: ple...@li...; Scott Hetherington; Mark Guerra >> Subject: Re: [plexil-support] Memory issue >> >> PS: The output of 'uname -a' should suffice to answer my question about your Unbuntu version… >> >> Mike > > > ------------------------------------------------------------------------------ > 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... > https://lists.sourceforge.net/lists/listinfo/plexil-support Chuck Fry Senior Software Engineer Dell | Services, Federal Government Office: 650 604 1882 Mobile: 408 230 2715 M/S 269-1, Building N269/260-7 NASA Ames Research Center Moffett Field, CA 94035-1000 I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me. |
|
From: Mark G. <Mar...@ti...> - 2014-03-14 10:17:07
|
Thanks for your help Mike. This is a curiousity question. Why has the development version of PLEXIL -3 not been released yet? Are there any plans to release it? Mark Guerra | Senior Software Architect | Tietronix Software Inc. | 1331 Gemini Ave. Suite 300 | Houston, TX 77058 +1 (281) 404-7244 | mg...@ti... | www.tietronix.com ________________________________________ From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...] Sent: Thursday, March 13, 2014 10:07 PM To: Catherine Szeto Cc: ple...@li...; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue Thanks, and glad you sent that. I was starting to build on a (virtual) 64-bit version of that Ubuntu, but will get the 32-bit machine to match yours. Hope to have the distribution posted tomorrow. Mike > Ah, sorry. Here is what I get from that command: > > Linux ubuntu 3.2.0-60-generic-pae #91-Ubuntu SMP Wed Feb 19 04:14:56 UTC 2014 i686 i686 i386 GNU/Linux > > Thanks, > Catherine > ________________________________________ > From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...] > Sent: Thursday, March 13, 2014 4:26 PM > To: Catherine Szeto > Cc: ple...@li...; Scott Hetherington; Mark Guerra > Subject: Re: [plexil-support] Memory issue > > PS: The output of 'uname -a' should suffice to answer my question about your Unbuntu version… > > Mike |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-14 03:07:38
|
Thanks, and glad you sent that. I was starting to build on a (virtual) 64-bit version of that Ubuntu, but will get the 32-bit machine to match yours. Hope to have the distribution posted tomorrow. Mike > Ah, sorry. Here is what I get from that command: > > Linux ubuntu 3.2.0-60-generic-pae #91-Ubuntu SMP Wed Feb 19 04:14:56 UTC 2014 i686 i686 i386 GNU/Linux > > Thanks, > Catherine > ________________________________________ > From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...] > Sent: Thursday, March 13, 2014 4:26 PM > To: Catherine Szeto > Cc: ple...@li...; Scott Hetherington; Mark Guerra > Subject: Re: [plexil-support] Memory issue > > PS: The output of 'uname -a' should suffice to answer my question about your Unbuntu version… > > Mike |
|
From: Catherine S. <Cat...@ti...> - 2014-03-14 02:10:45
|
Ah, sorry. Here is what I get from that command: Linux ubuntu 3.2.0-60-generic-pae #91-Ubuntu SMP Wed Feb 19 04:14:56 UTC 2014 i686 i686 i386 GNU/Linux Thanks, Catherine ________________________________________ From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mic...@na...] Sent: Thursday, March 13, 2014 4:26 PM To: Catherine Szeto Cc: ple...@li...; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue PS: The output of 'uname -a' should suffice to answer my question about your Unbuntu version… Mike |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-13 21:27:04
|
PS: The output of 'uname -a' should suffice to answer my question about your Unbuntu version… Mike |
|
From: Catherine S. <Cat...@ti...> - 2014-03-13 21:12:13
|
Ubuntu 12.04.4 LTS. Thanks for the help. Catherine From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...] Sent: Thursday, March 13, 2014 4:09 PM To: Catherine Szeto Cc: ple...@li...; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue Okay, thanks. What version of Ubuntu? I'll see if I can build a plexil-3 image for it. Mike On Mar 13, 2014, at 2:04 PM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: I'm using Linux ubuntu (to answer your question in another thread) and I'm using the "top" command. We were thinking if there was indeed some kind of reserved memory. We have expanded our virtual machine memory to 6 GB, but our Main.ple application seems to top off at around 4 GB (this is with all the plans added, not the initial 25), and then we start seeing errors. From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 4:02 PM To: Catherine Szeto Cc: ple...@li...<mailto:ple...@li...>; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue How are you measuring the memory usage? I've been told that PLEXIL may be reserving a fair amount of virtual memory that is not actually in use... Mike Mark answered the Plexil version question in a separate thread, as I do not know myself. I tried commenting out the Main.ple so about half of the code is used. The memory usage came to about 3.1 GB. Catherine From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 1:51 PM To: Catherine Szeto Cc: ple...@li...<mailto:ple...@li...>; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue Catherine, Your application just might be the largest PLEXIL plan yet, in number of nodes, plans, and total lines of PLEXIL. The previous largest in my recollection had about 600-800 nodes and about a dozen plans in all. We have not tested the system with an application of your size. A very important factor is the question Chuck asked: are you using the plexil-3 branch of our Sourceforge repository? If not, you should, as this has significantly better memory performance. Could you try halving the plan size, e.g. comment out some of the library declarations and calls, and see how this affects the memory size? This could help us characterize the memory bloat. Thanks, Mike On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: 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...<mailto: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 |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-13 21:09:26
|
Okay, thanks. What version of Ubuntu? I'll see if I can build a plexil-3 image for it. Mike On Mar 13, 2014, at 2:04 PM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: I'm using Linux ubuntu (to answer your question in another thread) and I'm using the "top" command. We were thinking if there was indeed some kind of reserved memory. We have expanded our virtual machine memory to 6 GB, but our Main.ple application seems to top off at around 4 GB (this is with all the plans added, not the initial 25), and then we start seeing errors. From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 4:02 PM To: Catherine Szeto Cc: ple...@li...<mailto:ple...@li...>; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue How are you measuring the memory usage? I've been told that PLEXIL may be reserving a fair amount of virtual memory that is not actually in use… Mike Mark answered the Plexil version question in a separate thread, as I do not know myself. I tried commenting out the Main.ple so about half of the code is used. The memory usage came to about 3.1 GB. Catherine From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 1:51 PM To: Catherine Szeto Cc: ple...@li...<mailto:ple...@li...>; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue Catherine, Your application just might be the largest PLEXIL plan yet, in number of nodes, plans, and total lines of PLEXIL. The previous largest in my recollection had about 600-800 nodes and about a dozen plans in all. We have not tested the system with an application of your size. A very important factor is the question Chuck asked: are you using the plexil-3 branch of our Sourceforge repository? If not, you should, as this has significantly better memory performance. Could you try halving the plan size, e.g. comment out some of the library declarations and calls, and see how this affects the memory size? This could help us characterize the memory bloat. Thanks, Mike On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: 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...<mailto: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 |
|
From: Catherine S. <Cat...@ti...> - 2014-03-13 21:04:40
|
I'm using Linux ubuntu (to answer your question in another thread) and I'm using the "top" command. We were thinking if there was indeed some kind of reserved memory. We have expanded our virtual machine memory to 6 GB, but our Main.ple application seems to top off at around 4 GB (this is with all the plans added, not the initial 25), and then we start seeing errors. From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...] Sent: Thursday, March 13, 2014 4:02 PM To: Catherine Szeto Cc: ple...@li...; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue How are you measuring the memory usage? I've been told that PLEXIL may be reserving a fair amount of virtual memory that is not actually in use... Mike Mark answered the Plexil version question in a separate thread, as I do not know myself. I tried commenting out the Main.ple so about half of the code is used. The memory usage came to about 3.1 GB. Catherine From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 1:51 PM To: Catherine Szeto Cc: ple...@li...<mailto:ple...@li...>; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue Catherine, Your application just might be the largest PLEXIL plan yet, in number of nodes, plans, and total lines of PLEXIL. The previous largest in my recollection had about 600-800 nodes and about a dozen plans in all. We have not tested the system with an application of your size. A very important factor is the question Chuck asked: are you using the plexil-3 branch of our Sourceforge repository? If not, you should, as this has significantly better memory performance. Could you try halving the plan size, e.g. comment out some of the library declarations and calls, and see how this affects the memory size? This could help us characterize the memory bloat. Thanks, Mike On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: 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...<mailto: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 |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-13 21:01:51
|
How are you measuring the memory usage? I've been told that PLEXIL may be reserving a fair amount of virtual memory that is not actually in use… Mike Mark answered the Plexil version question in a separate thread, as I do not know myself. I tried commenting out the Main.ple so about half of the code is used. The memory usage came to about 3.1 GB. Catherine From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 1:51 PM To: Catherine Szeto Cc: ple...@li...<mailto:ple...@li...>; Scott Hetherington; Mark Guerra Subject: Re: [plexil-support] Memory issue Catherine, Your application just might be the largest PLEXIL plan yet, in number of nodes, plans, and total lines of PLEXIL. The previous largest in my recollection had about 600-800 nodes and about a dozen plans in all. We have not tested the system with an application of your size. A very important factor is the question Chuck asked: are you using the plexil-3 branch of our Sourceforge repository? If not, you should, as this has significantly better memory performance. Could you try halving the plan size, e.g. comment out some of the library declarations and calls, and see how this affects the memory size? This could help us characterize the memory bloat. Thanks, Mike On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: 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...<mailto: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 |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-13 21:00:10
|
That is indeed our more recent PLEXIL distribution, but sadly it is quite behind the development branch most PLEXIL users are currently using. The development branch is available as source code only, and is not as easy to build as the main branch from which the distribution you have is based. The newer development branch of PLEXIL, 'plexil-3', has an executive that is *much* improved over the one you're using, for speed and memory performance in particular. Your plans should be fully compatible, however the interfacing framework's API has changed. Much is backwards compatible, but I'm not positive that your existing interface adapter will work as is. The required changes should not be severe. I may be able build you a binary distribution of plexil-3 soon if you are interested. In any case, could you tell me what operating system you are running PLEXIL on? Mike On Mar 13, 2014, at 12:45 PM, Mark Guerra <Mar...@ti...<mailto:Mar...@ti...>> wrote: Here is downloaded image for PLEXIL we have installed. plexil-250-linux-i686.tar.gz Mark Guerra | Senior Software Architect | Tietronix Software Inc. | 1331 Gemini Ave. Suite 300 | Houston, TX 77058 +1 (281) 404-7244 | mg...@ti...<mailto:mg...@ti...> | www.tietronix.com<http://www.tietronix.com/> ________________________________ From: Catherine Szeto Sent: Thursday, March 13, 2014 10:49 AM To: Mark Guerra; Lui Wang (Lui...@na...<mailto:Lui...@na...>) Subject: FW: [plexil-support] Memory issue Can either of you answer Chuck's question for me? Thanks. From: Fry, Charles R. {Chuck} (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:chu...@na...<http://nasa.gov>] Sent: Thursday, March 13, 2014 10:47 AM To: Catherine Szeto Cc: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)]; Mark Guerra; ple...@li...<mailto:ple...@li...>; Scott Hetherington Subject: Re: [plexil-support] Memory issue Are you using the "released" version or the plexil-3 development branch? We believe we have significantly improved memory management in the development version, but there may be issues building it in some environments. -- Chuck On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: 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...<mailto: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 ------------------------------------------------------------------------------ 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 Chuck Fry Senior Software Engineer Dell | Services, Federal Government Office: 650 604 1882 Mobile: 408 230 2715 M/S 269-1, Building N269/260-7 NASA Ames Research Center Moffett Field, CA 94035-1000 I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me. |
|
From: Catherine S. <Cat...@ti...> - 2014-03-13 20:47:25
|
Mark answered the Plexil version question in a separate thread, as I do not know myself.
I tried commenting out the Main.ple so about half of the code is used. The memory usage came to about 3.1 GB.
Catherine
From: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:mic...@na...]
Sent: Thursday, March 13, 2014 1:51 PM
To: Catherine Szeto
Cc: ple...@li...; Scott Hetherington; Mark Guerra
Subject: Re: [plexil-support] Memory issue
Catherine,
Your application just might be the largest PLEXIL plan yet, in number of nodes, plans, and total lines of PLEXIL. The previous largest in my recollection had about 600-800 nodes and about a dozen plans in all. We have not tested the system with an application of your size.
A very important factor is the question Chuck asked: are you using the plexil-3 branch of our Sourceforge repository? If not, you should, as this has significantly better memory performance.
Could you try halving the plan size, e.g. comment out some of the library declarations and calls, and see how this affects the memory size? This could help us characterize the memory bloat.
Thanks,
Mike
On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote:
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...<mailto: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
|
|
From: Mark G. <Mar...@ti...> - 2014-03-13 19:48:14
|
Here is downloaded image for PLEXIL we have installed. plexil-250-linux-i686.tar.gz Mark Guerra | Senior Software Architect | Tietronix Software Inc. | 1331 Gemini Ave. Suite 300 | Houston, TX 77058 +1 (281) 404-7244 | mg...@ti...<mailto:mg...@ti...> | www.tietronix.com<http://www.tietronix.com/> ________________________________ From: Catherine Szeto Sent: Thursday, March 13, 2014 10:49 AM To: Mark Guerra; Lui Wang (Lui...@na...) Subject: FW: [plexil-support] Memory issue Can either of you answer Chuck's question for me? Thanks. From: Fry, Charles R. {Chuck} (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] [mailto:chu...@na...] Sent: Thursday, March 13, 2014 10:47 AM To: Catherine Szeto Cc: Dalal, Michael (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)]; Mark Guerra; ple...@li...; Scott Hetherington Subject: Re: [plexil-support] Memory issue Are you using the "released" version or the plexil-3 development branch? We believe we have significantly improved memory management in the development version, but there may be issues building it in some environments. -- Chuck On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote: 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...<mailto: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 ------------------------------------------------------------------------------ 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 Chuck Fry Senior Software Engineer Dell | Services, Federal Government Office: 650 604 1882 Mobile: 408 230 2715 M/S 269-1, Building N269/260-7 NASA Ames Research Center Moffett Field, CA 94035-1000 I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me. |
|
From: Dalal, M. (ARC-TI)[S. G. T. I. (S. Inc.)] <mic...@na...> - 2014-03-13 18:51:27
|
Catherine,
Your application just might be the largest PLEXIL plan yet, in number of nodes, plans, and total lines of PLEXIL. The previous largest in my recollection had about 600-800 nodes and about a dozen plans in all. We have not tested the system with an application of your size.
A very important factor is the question Chuck asked: are you using the plexil-3 branch of our Sourceforge repository? If not, you should, as this has significantly better memory performance.
Could you try halving the plan size, e.g. comment out some of the library declarations and calls, and see how this affects the memory size? This could help us characterize the memory bloat.
Thanks,
Mike
On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote:
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...<mailto: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
|
|
From: Catherine S. <Cat...@ti...> - 2014-03-13 16:28:29
|
One more note to add: I searched for nodes by counting the number of breakpoints "</Node>" in all the plx files. I'm not sure if this is the count you were looking for.
From: Catherine Szeto
Sent: Thursday, March 13, 2014 10:41 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
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...<mailto: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
|
|
From: Fry, C. R. {C. (ARC-TI)[S. G. T. I. (S. Inc.)] <chu...@na...> - 2014-03-13 15:47:11
|
Are you using the "released" version or the plexil-3 development branch? We believe we have significantly improved memory management in the development version, but there may be issues building it in some environments.
-- Chuck
On Mar 13, 2014, at 8:40 AM, Catherine Szeto <Cat...@ti...<mailto:Cat...@ti...>> wrote:
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...<mailto: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
------------------------------------------------------------------------------
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...
https://lists.sourceforge.net/lists/listinfo/plexil-support
Chuck Fry
Senior Software Engineer
Dell | Services, Federal Government
Office: 650 604 1882 Mobile: 408 230 2715
M/S 269-1, Building N269/260-7
NASA Ames Research Center
Moffett Field, CA 94035-1000
I do not speak for Dell, SGT, Code TI, or NASA, nor do they speak for me.
|
|
From: Catherine S. <Cat...@ti...> - 2014-03-13 15:40:39
|
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
|
|
From: Catherine S. <Cat...@ti...> - 2014-03-13 15:21:47
|
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...
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
|