Re: Speeding up the ocnPrint() function
- From: Svenn Are Bjerkem <svenn.bjerkem@xxxxxxxxxxxxxx>
- Date: Fri, 01 Jun 2007 21:36:07 -0700
On Jun 1, 6:14 am, Stephen Greenwood <stephen.greenw...@xxxxxxxxx>
wrote:
I noticed that ocnPrint() is reasonably fast until the data gets above
a certain size. I don't know what that size is, but one does get a
warning if the printing exceeds 10000 points. To get around this, I
simply embedded the ocnPrint() statement in a for() loop, printing 1%
of the points each time through the loop. The index of the loop is
used to control the ?from and ?to switches. Obviously the 1% is
arbitrary, and can be increased or decreased for smaller or larger
numbers of points, respectively.
Thanks for the input.
How much physical memory does your workstation have? I have always
been thinking that this is the reason for any skill list operation to
start swapping, which kills performance. Maybe ocnPrint uses a list
operation that first expands the whole list, or wants to build the
whole list before printing to disk. We don't know, and will never
know, since we don't have the source code of it....
--
Svenn
.
- Follow-Ups:
- Re: Speeding up the ocnPrint() function
- From: Stephen Greenwood
- Re: Speeding up the ocnPrint() function
- References:
- Speeding up the ocnPrint() function
- From: Stephen Greenwood
- Speeding up the ocnPrint() function
- Prev by Date: Re: keypad (numbers on the right) map
- Next by Date: Re: Results update using Analog Environment
- Previous by thread: Speeding up the ocnPrint() function
- Next by thread: Re: Speeding up the ocnPrint() function
- Index(es):
Relevant Pages
|