[m-rev.] for review: change the way IO actions are handled in the declarative debugger

[Ian MacLarty]

On 17 Jun 2005, at 02:51, Julien Fischer wrote:

>
>
> On Wed, 15 Jun 2005, Ian MacLarty wrote:
>
>> For review by anyone.
>>
>> Estimated hours taken: 4
>> Branches: main
>>
>> Do not build an IO action map to pass around to predicates in the
>> declarative debugger that need access to IO actions.
>> Instead look these up directly in the IO state.
>> When using the declarative debugger to debug the Mercury compiler 
>> invoked
>> on typecheck.m, which generates about 2.3 million IO actions,
>> this change reduces the memory consumption by roughly half and reduces
>> the delay between the end of execution trace generation and the 
>> asking of the
>> first question from about 30 seconds to about 2 seconds.
>>
> That's great.
> (Out of curiosity how does it do with make_hlds.m, which is about three
> times the size of typecheck.m?)
>

Compiling make_hlds.m generates 3.5 million IO actions and the delay 
after generating the initial trace is still only a few seconds (though 
the initial trace takes about 5 minutes to generate).  The RSS at the 
first question is about 220MB.

Ian.

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------