[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] Rebuild AspectJ project after eclipse restart
- From: Gil Sagi <gilmod@xxxxxxxxx>
- Date: Sun, 10 Oct 2010 13:45:39 +0200
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Mc6LNh1Of0e762AeISREwTDyH5h/CImOdRevqYvud40=; b=KjfZywgGQkwycaXMQSSg+y+xVHvnOs9CTA866KIis6gHmACxPFeLzVblfm6Mf5figy YQ7HRodbrRWuoAR7+Xa4XdQvbnU9sdu6jNceIcw58+F7FI5PB3e5VqclUEFv2NjQ/pO+ pJ0a/ESHH3A+GgELMVJD/tzUcRegXmi7AXca0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=i39QqKt1CfA3hB4iPq1mP9Sk5Wf2p+06jdMATLc8sss+w81cGqAkPPnFTACjI8A/U+ Ij8XExE61yD8KHNlLgFHsA78ui/sJZvscmNAQ71AJz5WRjEa2vxA0Huj9A0xJZQMRFj8 2x9vk6Qld7wLXhBFHOXqO2Gm4Fv8r52qxVRQk=
When I'm building the project without the heap optimization (-Xset:minimalModel=true,typeDemotion=true)the heap is reaching my max heapsetting (~1400) which causes the GC to run again and again which seems to affect the performance and the full build takes about 8 minutes.
Now when I'm trying to build with the optimization it seems there is a big reduction in the heap usage but the build is very very slow and takes more than 1 hour (it didn't finish yet...).
So actually I cannot use this optimization although the heap state is absolutely better.
Do you have any idea?
2010/10/10 Andy Clement <andrew.clement@xxxxxxxxx>
> Currently the Eclipse downside is the memory consumption of the weavingThat is a long time for a full build... Is it by any chance due to
> process - it takes about 8 minutes and the heap is getting up to 1400MB so
> restart the Eclipse from time to time is a use-case we cannot ignore.
the heap getting relatively full and then GC thrashing going on? (so
not actually running out of memory, but running on the limit). If so
you could try those AJDT memory settings I mentioned in the 1.6.10
readme, they should reduce the heap usage (if you try them and they
don't, that is interesting feedback...) -