public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Diego Novillo <dnovillo@google.com>
Cc: Alexandre Oliva <aoliva@redhat.com>, gcc@gcc.gnu.org
Subject: VTA compile time memory usage comparison
Date: Fri, 03 Jul 2009 10:15:00 -0000	[thread overview]
Message-ID: <20090703101450.GU4462@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <b798aad50906081035x7f14a6bdv62c3a05fd14e8a82@mail.gmail.com>

On Mon, Jun 08, 2009 at 01:35:34PM -0400, Diego Novillo wrote:
> On Sun, Jun 7, 2009 at 16:04, Alexandre Oliva<aoliva@redhat.com> wrote:
> 
> > So the question is, what should I measure?  Memory use for any specific
> > set of testcases, summarized over a bootstrap with memory use tracking
> > enabled, something else?  Likewise for compile time?  What else?
> 
> Some quick measurements I'd be interested in:
> 
> - Size of the IL over some standard code bodies
>   (http://gcc.gnu.org/wiki/PerformanceTesting).

> - Memory consumption in cc1/cc1plus at -Ox -g over that set of apps.

Here are data comparing trunk@148582 (last merge point to VTA branch) with
vta@149180 (current VTA branch head), using maxmem2.sh and maxmem-pipe2.py.
Both compilers were built with --enable-checking=release, all numbers are
on x86_64-linux from cc1 resp. cc1plus (*.i resp. *.ii) with -g -quiet and
the options listed in the header line.

The only major compile time memory consumption problem is in VARIOUS/,
particularly pr28071.i where var-tracking goes through roof, I hope Alex
will look into it, worst case we could just silently turn off
flag_var_tracking_assignments in var-tracking.c for functions which have
too many basic blocks and too many VALUEs to track.

I'm now running compilations with -ftime-report, once that finishes will
post statistics for compile time as well, then size of IL.

			-O0-m64	-O0-m32	-O1-m64	-O1-m32	-O2-m64	-O2-m32	-O3-m64	-O3-m32	-Os-m64	-Os-m32
GCC trunk@148582 avg	103772	102936	105455	104689	106334	105539	108212	107044	105339	104666
GCC vta@149180   avg	103773	102937	106076	105426	106963	106324	108964	107892	105864	105203
vta@149180/trunk@148582	100.00%	100.00%	100.59%	100.70%	100.59%	100.74%	100.69%	100.79%	100.50%	100.51%
GCC trunk@148582 max	528254	460362	587570	542154	598130	533138	625174	544654	591410	555526
GCC vta@149180   max	528254	460362	579338	540282	598014	547914	627214	561434	578970	553646
vta@149180/trunk@148582	100.00%	100.00%	98.60%	99.65%	99.98%	102.77%	100.33%	103.08%	97.90%	99.66%
FF3D trunk@148582 avg	160478	160379	169280	170735	174005	175407	179056	179874	164380	165596
FF3D vta@149180   avg	160463	160384	171352	173741	176746	178873	182519	183965	165770	167263
vta@149180/trunk@148582	99.99%	100.00%	101.22%	101.76%	101.58%	101.98%	101.93%	102.27%	100.85%	101.01%
FF3D trunk@148582 max	494298	493310	497114	492538	509234	508778	529734	540582	476798	493110
FF3D vta@149180   max	494298	493338	515690	517554	531498	530806	542822	552638	514798	534822
vta@149180/trunk@148582	100.00%	100.01%	103.74%	105.08%	104.37%	104.33%	102.47%	102.23%	107.97%	108.46%
MICO trunk@148582 avg	270379	240593	276524	248775	278922	251851	282331	254687	273297	246126
MICO vta@149180   avg	270328	240570	278185	251241	280705	254305	284368	257374	274451	247978
vta@149180/trunk@148582	99.98%	99.99%	100.60%	100.99%	100.64%	100.97%	100.72%	101.06%	100.42%	100.75%
MICO trunk@148582 max	497802	494486	537502	522602	528098	519598	557086	544478	528158	527110
MICO vta@149180   max	497838	494506	538998	524282	533038	522418	566886	550298	545302	553194
vta@149180/trunk@148582	100.01%	100.00%	100.28%	100.32%	100.94%	100.54%	101.76%	101.07%	103.25%	104.95%
SPEC2K trunk@148582 avg	101353	101091	102610	102519	103434	103358	105819	105165	102910	102884
SPEC2K vta@149180   avg	101349	101092	103087	103067	103936	103914	106482	105914	103360	103395
vta@149180/trunk@148582	100.00%	100.00%	100.46%	100.53%	100.49%	100.54%	100.63%	100.71%	100.44%	100.50%
SPEC2K trunk@148582 max	172526	172678	188594	188810	192194	193514	204014	202330	186690	189914
SPEC2K vta@149180   max	172526	172674	189394	192394	195182	197266	205002	206714	187870	192654
vta@149180/trunk@148582	100.00%	100.00%	100.42%	101.90%	101.55%	101.94%	100.48%	102.17%	100.63%	101.44%
TRAMP3Dtrunk@148582 avg	686766	685898	893478	889398	919662	942746	996782	995498	891466	893930
TRAMP3Dvta@149180   avg	687558	686494	1030534	1024634	1023046	1020642	1045182	1053774	891838	897942
vta@149180/trunk@148582	100.12%	100.09%	115.34%	115.21%	111.24%	108.26%	104.86%	105.85%	100.04%	100.45%
TRAMP3Dtrunk@148582 max	686766	685898	893478	889398	919662	942746	996782	995498	891466	893930
TRAMP3Dvta@149180   max	687558	686494	1030534	1024634	1023046	1020642	1045182	1053774	891838	897942
vta@149180/trunk@148582	100.12%	100.09%	115.34%	115.21%	111.24%	108.26%	104.86%	105.85%	100.04%	100.45%
DLV trunk@148582 avg	239153	237855	260962	261421	263187	263827	270711	268845	247990	248256
DLV vta@149180   avg	239135	237804	264511	265722	267777	269264	275713	275005	250084	250658
vta@149180/trunk@148582	99.99%	99.98%	101.36%	101.65%	101.74%	102.06%	101.85%	102.29%	100.84%	100.97%
DLV trunk@148582 max	375554	376498	383990	383798	385438	388962	401438	397650	381074	382142
DLV vta@149180   max	375558	376462	386966	392262	408638	412070	421038	427414	382886	383446
vta@149180/trunk@148582	100.00%	99.99%	100.78%	102.21%	106.02%	105.94%	104.88%	107.48%	100.48%	100.34%
VARIOUStrunk@148582 avg	415948	416633	518190	544250	684925	709474	703472	725017	565568	708509
VARIOUSvta@149180   avg	415933	416624	615444	646627	3143720	3642774	3133712	3607254	1646542	3351722
vta@149180/trunk@148582	100.00%	100.00%	118.77%	118.81%	458.99%	513.45%	445.46%	497.54%	291.13%	473.07%
VARIOUStrunk@148582 max	544654	547038	686858	705486	1388662	1511014	1413242	1511062	835282	1514758
VARIOUSvta@149180   max	544714	547190	953818	953810	13096222	15577234	13095842	15550054	5811502	14301914
vta@149180/trunk@148582	100.01%	100.03%	138.87%	135.20%	943.08%	1030.91%	926.65%	1029.08%	695.75%	944.17%

	Jakub

  parent reply	other threads:[~2009-07-03 10:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 10:06 VTA merge? Alexandre Oliva
2009-06-05 10:19 ` Richard Guenther
2009-06-05 10:53   ` Alexandre Oliva
2009-06-05 11:18     ` Richard Guenther
2009-06-06  8:12   ` Eric Botcazou
2009-06-07 21:32     ` Alexandre Oliva
2009-06-08  2:49       ` Eric Botcazou
2009-06-08 21:31         ` Alexandre Oliva
2009-06-05 10:42 ` Joseph S. Myers
2009-06-05 11:11   ` Alexandre Oliva
2009-06-05 12:28 ` David Edelsohn
2009-06-05 19:18   ` Alexandre Oliva
2009-06-05 20:56     ` Daniel Berlin
2009-06-07 20:04       ` Alexandre Oliva
2009-06-08 16:19         ` Frank Ch. Eigler
2009-06-08 17:35         ` Diego Novillo
2009-06-08 21:04           ` Alexandre Oliva
2009-06-08 21:30             ` Joe Buck
2009-06-09  1:15               ` Alexandre Oliva
2009-06-18 11:04             ` Diego Novillo
2009-06-18 20:58               ` Alexandre Oliva
2009-06-18  8:37           ` Alexandre Oliva
2009-06-18 10:00             ` Paolo Bonzini
2009-06-18 12:31               ` Michael Matz
2009-06-18 13:35                 ` Diego Novillo
2009-06-18 18:05                   ` Gerald Pfeifer
2009-06-21  5:01             ` Alexandre Oliva
2009-06-21 11:02               ` Richard Guenther
2009-06-21 11:38                 ` Richard Guenther
2009-06-21 11:50                   ` Richard Guenther
2009-07-01  5:26                   ` Alexandre Oliva
2009-07-03 10:15           ` Jakub Jelinek [this message]
2009-06-05 22:11     ` Machine Description Template? Graham Reitz
2009-06-05 22:31       ` Ramana Radhakrishnan
2009-06-05 22:46       ` Michael Hope
2009-06-05 22:55         ` Graham Reitz
2009-06-09  8:57           ` Martin Guy
2009-06-05 23:48       ` Jeff Law
2009-06-12 21:36       ` Michael Meissner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090703101450.GU4462@tyan-ft48-01.lab.bos.redhat.com \
    --to=jakub@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).