"Laurynas Biveinis" <[EMAIL PROTECTED]> writes:
> Hi,
>
> > > combine.c: top mem usage: 52180k (13915k). GC execution time 0.66
> > > (0.61) 4% (4%). User running time: 0m16 (0m14).
> >
> > Are these with checking on or off? Normally checking is on, you have
> > to go out of your way to turn it
On 25/06/06, Laurynas Biveinis <[EMAIL PROTECTED]> wrote:
2006/6/25, Paulo J. Matos <[EMAIL PROTECTED]>:
> > combine.c: top mem usage: 52180k (13915k). GC execution time 0.66
> > (0.61) 4% (4%). User running time: 0m16 (0m14).
> >
>
> How are you collecting top mem usage?
Sorry, that's not the t
2006/6/25, Paulo J. Matos <[EMAIL PROTECTED]>:
> combine.c: top mem usage: 52180k (13915k). GC execution time 0.66
> (0.61) 4% (4%). User running time: 0m16 (0m14).
>
How are you collecting top mem usage?
Sorry, that's not the top mem usage, but rather peak GC allocated
bytes. Determining them
On 23/06/06, Laurynas Biveinis <[EMAIL PROTECTED]> wrote:
I'm still waiting for the testsuite to complete (it's been running
just for about 24 hours so far). In the meanwhile I'd like to discuss
the first performance results, which I've put on the Wiki:
First number is GCC with Boehm's GC and th
2006/6/23, David Nicol <[EMAIL PROTECTED]>:
Is it possible to turn garbage collection totally off for a null-case
run-time comparison or would that cause thrashing except for very
small jobs?
It should be possible to adopt ggc-none for usage in GCC proper with
little effort. Shouldn't cause tra
On Jun 24, 2006, at 1:43 PM, Laurynas Biveinis wrote:
An excellent suggestion, although my primary working platform is
valgrind-less Cygwin, but I will find a way to gather cache usage
data.
You could try to use Vtune though.
Thanks,
Andrew Pinski
Hi,
> combine.c: top mem usage: 52180k (13915k). GC execution time 0.66
> (0.61) 4% (4%). User running time: 0m16 (0m14).
Are these with checking on or off? Normally checking is on, you have
to go out of your way to turn it off. If it were on, the real
numbers are going to look much worse tha
2006/6/23, Steven Bosscher <[EMAIL PROTECTED]>:
Don't write off Boehm's GC just yet. You can't expect to beat
something that has seen a lot of tuning for GCC with something that
you got working only a few days ago. There are a lot of special tricks
especially in ggc-page that may put it at an ad
On 6/23/06, Laurynas Biveinis <[EMAIL PROTECTED]> wrote:
What do you think?
Is it possible to turn garbage collection totally off for a null-case
run-time comparison or would that cause thrashing except for very
small jobs?
--
David L Nicol
"if life were like Opera, this would probably
have po
>
> On Jun 23, 2006, at 8:51 AM, Laurynas Biveinis wrote:
> > First number is GCC with Boehm's GC and the number in parentheses is
> > GCC with page collector.
> >
> > combine.c: top mem usage: 52180k (13915k). GC execution time 0.66
> > (0.61) 4% (4%). User running time: 0m16 (0m14).
>
> Are the
On Jun 23, 2006, at 8:51 AM, Laurynas Biveinis wrote:
First number is GCC with Boehm's GC and the number in parentheses is
GCC with page collector.
combine.c: top mem usage: 52180k (13915k). GC execution time 0.66
(0.61) 4% (4%). User running time: 0m16 (0m14).
Are these with checking on or of
On 6/23/06, Laurynas Biveinis <[EMAIL PROTECTED]> wrote:
All in all, IMHO this data favours against Boehm's GC in GCC. But
before deciding I would like to enable generational GC features, if
that will help with run time. On the other hand, I don't see how peak
memory usage could be reduced.
What
I'm still waiting for the testsuite to complete (it's been running
just for about 24 hours so far). In the meanwhile I'd like to discuss
the first performance results, which I've put on the Wiki:
First number is GCC with Boehm's GC and the number in parentheses is
GCC with page collector.
combin
13 matches
Mail list logo
