Re: [Boost-users] Max Boost Fusion tuple parameters

Subject: Re: [Boost-users] Max Boost Fusion tuple parameters
From: Larry Evans (cppljevans_at_[hidden])
Date: 2013-06-14 10:08:17

On 06/14/13 04:39, Slava wrote:
> On Thu, 13 Jun 2013 14:27:30 +0200, Larry Evans
> <cppljevans_at_[hidden]> wrote:
> 
>> It also appears that when TUPLE_SIZE >=100,
>> compile time goes up linearly.

I think that linear remark was wrong.  It goes up
by a factor of about 2 between 100 and 200 and
then by another factor of 2 between 200 and 300.
That's exponential IIRC :(  Of course I could be
misunderstanding again.  It happens :(

> 
> 
> Take a look at memory usage either, as soon as it starts swapping, it's
> far from linear. Your peers will curse you for this code. CDT indexer
> (eclipse) takes a lot time and memory on such constructs.
> The size of the produced binary (due to debug info for all these small
> inlined internal helper functions) must not be forgotten. It's hard to
> justify half-Gb executable to the colleagues.
> 
> -- Slava
Ah!  Thanks for the tip.  I had no idea that was the case.
Would spirit's fusion do any better?  Maybe a better question
is would there be any reason for such large tuples.  I asked
Rodrigo that question in another post; however, I've not heard
back from him.

--Larry