OK - I think I *may* have got to the bottom of this. I've fixed two
problems today - one in ARY (I was allocating the memory to hold a
mapped array twice rather than once), and one in NDG (I was simply
annulling temporary HDS objects, rather than annulling them AND
erasing them).
Using Malcolm's collapser.icl script, I watch the size of the
temporary HDS file and it now stays stable, rather than increasing
wildly in size. However, there is still a slow drift upwards in file
size, and I saw a sudden one-off large increase in file size at about
invocation number 18. Can't think why this sudden increase should
occur after the file size had been been stable up to that point.
David
On 6 December 2010 13:05, Brian McIlwrath <[log in to unmask]> wrote:
> Hi Brian,
> Can you give me a command line and a data set that
> demonstrates the ARY problem? Trying collapse out on a random data set
> doesn't show any problem (i.e. all locators issued by dat_temp are
> annulled before exit).
>
> David
>
> Hi David,
>
> I will send you direct details on what I am looking to see the ARY
> problem
> - which still seems to be present (in fact the correction to NDG has
> exposed it better!
>
> On the loop on COLLAPSE (which will be in the ICL procedure I am about
> to send you!) the scores are:-
>
> Before iteration 1 - 8 locators used in HD by the parameter system
> After iteration 1 - 37 locators including ARY_TEMP plus lots of ARY_1,
> ARY_4, ARY_6, ARY_9 etc. etc.
> After iteration 2 - 65 locators (lots more ARY_nnn ones)
>
> I *THOUGHT* I only saw ARY_TEMP before! However I have totally rebuilt
> ARY (again!)
>
> Brian
>
|