This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: WPA stream_out form & memory consumption
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Martin Liška <mliska at suse dot cz>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 3 Apr 2014 00:46:42 +0200
- Subject: Re: WPA stream_out form & memory consumption
- Authentication-results: sourceware.org; auth=none
- References: <53286192 dot 3030600 at suse dot cz> <20140325205021 dot GA6581 at atrey dot karlin dot mff dot cuni dot cz> <5333E6B8 dot 3000504 at suse dot cz> <5333F3D3 dot 1010009 at suse dot cz> <533C1B04 dot 40407 at suse dot cz> <533C36C8 dot 6090604 at suse dot cz>
> Previous email presents a bit misleading graphs (influenced by
> --enable-gather-detailed-mem-stats).
>
> Firefox:
> -flto=9, WPA peak: 8GB, LTRANS peak: 8GB
> -flto=4, WPA peak: 5GB, LTRANS peak: 3.5GB
> -flto=1, WPA peak: 3.5GB, LTRANS peak: ~1GB
>
> These data shows that parallel WPA streaming increases short-time
> memory footprint by 4.5GB for -flto=9 (respectively by 1.5GB in case
> of -flto=4).
>
> For more details, please see the attachment.
Aha, --enable-gather-detailed-mem-stats maintains on-side hashtable tracking all
ggc allocations so it almost doubles memory use. That explains the disproportions
in between GGC use and your graphs. Can you, perhaps, also get chromium graphs
without detailed stats?
Honza
>
> Martin