On 4/12/2012 5:05 PM, Michael Haberler wrote:
> Am 12.04.2012 um 22:57 schrieb Kenneth Lerman:
>
>> I guess your style is more subtle than mine.
>>
>> I think I would just record everything whether or not it changed.
>> Hmmm... if we store 1000 bytes at each step for a million (executed)
>> line program. That's "only" a gig. Small potatoes by today's standards.
> When I started working on the remapping stuff sizeof(_setup) was around 140 
> Kbytes.
>
> I shrunk it to roundabout 80kB, by replacing several fixed size structures by 
> std::map, std::set etc.
Then I would give up on the fixed length records, provide an index, and 
store only the differences using some clever (hopefully off the shelf) 
compression scheme.

Ken
>
>> If you use fixed length records, you can even access them randomly. Add
>> some indexing, and you can go directly to a line number.
>>
>> Ken
>>
>> On 4/12/2012 3:05 PM, Michael Haberler wrote:
>>> Ken,
>>>
>>> ...
>>>>> lets look at 1): Interp state as per _setup currently has some 140+ 
>>>>> variables, including maps, sets and arrays. Plus, there's some implicit 
>>>>> state in canon static
> ...
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to