Displaying 5 results from an estimated 5 matches for "groonga".
Did you mean:
groonga's
2016 Jan 14
3
High memory use and LVI/Correlated Value Propagation
...ways the LVI infrastructure could be
> made more memory efficient. Fixing the existing code to be memory efficient
> is the right approach. Only once there's no more low hanging fruit should
> we even consider clamping the search.
Memory efficiency is only half of the problem. I.e. groonga's expr.c
needs 4m to build on my laptop, a 2.7GHz i7. That doesn't sound
reasonable for a -O2. Unlike the GVN issue, the cases I have run into do
finish after a(n unreasonable) while, so at least it is not trivially
superlinear.
Joerg
2016 Jan 14
5
High memory use and LVI/Correlated Value Propagation
...ore memory efficient. Fixing the existing code to be
> memory efficient
> > is the right approach. Only once there's no more low hanging
> fruit should
> > we even consider clamping the search.
>
> Memory efficiency is only half of the problem. I.e. groonga's expr.c
> needs 4m to build on my laptop, a 2.7GHz i7. That doesn't sound
> reasonable for a -O2. Unlike the GVN issue, the cases I have run
> into do
> finish after a(n unreasonable) while, so at least it is not trivially
> superlinear.
>
>
>
&g...
2016 Jan 14
3
High memory use and LVI/Correlated Value Propagation
...efficient. Fixing the existing code to be memory
> > efficient
> > > is the right approach. Only once there's no more low hanging fruit
> > should
> > > we even consider clamping the search.
> >
> > Memory efficiency is only half of the problem. I.e. groonga's expr.c
> > needs 4m to build on my laptop, a 2.7GHz i7. That doesn't sound
> > reasonable for a -O2. Unlike the GVN issue, the cases I have run into do
> > finish after a(n unreasonable) while, so at least it is not trivially
> > superlinear.
> >
>
>...
2016 Jan 13
5
High memory use and LVI/Correlated Value Propagation
Hi all,
with the current trunk I have two major cases where clang needs more
than 2GB memory for compiling programs with -O2. One is related to GVN
and MemoryDependenceAnalysis and has a pending patch. The other is
related to the Correlated Value Propagation and Lazy Value Information
cache. Attached is a heap profile for one of the relevant test cases.
Looking at the sources, I don't see any
2016 Jan 14
2
High memory use and LVI/Correlated Value Propagation
...the right approach. Only once there's no more low hanging
> > > > > fruit
>
> > > > should
>
> > > > > we even consider clamping the search.
>
> > > >
>
> > > > Memory efficiency is only half of the problem. I.e. groonga's
> > > > expr.c
>
> > > > needs 4m to build on my laptop, a 2.7GHz i7. That doesn't sound
>
> > > > reasonable for a -O2. Unlike the GVN issue, the cases I have
> > > > run
> > > > into do
>
> > > > finish...