Bug 142126

Summary:	utilizing multiple CPUs for Java compiler
Product:	[Eclipse Project] JDT	Reporter:	Sujee Maniyam <eclipse2>
Component:	Core	Assignee:	Kent Johnson <kent_johnson>
Status:	VERIFIED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	david_audel, eric, jerome_lanneluc, nirav.thaker+eclipse-boogz
Version:	3.0
Target Milestone:	3.4 M7
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	151053

Description Sujee Maniyam

2006-05-16 20:54:24 EDT

With multi-core CPUs becoming affordable, I think it is about time that eclipse JDT build should took advantage of available CPUs.  Some thing like 'make -j ' flag.  Number of CPUs to be used could be made configurable in Preferences

Comment 1 Benjamin Muskalla

2008-04-03 16:44:49 EDT

I think this is a dup of bug 126121

Comment 2 Frederic Fusier

2008-04-04 04:36:31 EDT

(In reply to comment #1)
> I think this is a dup of bug 126121
> 
Indeed, thanks for pointing this.


*** This bug has been marked as a duplicate of bug 126121 ***

Comment 3 Jerome Lanneluc

2008-04-15 10:27:48 EDT

Reopening as this is not really a dup of bug 126121. Bug 126121 is about parallelizing the whole build process. Here the request is to ensure that the compiler uses multiple CPUs when available.

Comment 4 Jerome Lanneluc

2008-04-15 10:28:42 EDT

Reassigning to Kent that released this support on Friday without associating a bug to his changes.

Comment 5 Jerome Lanneluc

2008-04-15 10:30:04 EDT

*** Bug 225646 has been marked as a duplicate of this bug. ***

Comment 6 Jerome Lanneluc

2008-04-15 10:31:25 EDT

This was released for 3.4M7 on Friday.

Comment 7 Jerome Lanneluc

2008-04-15 10:38:36 EDT

In case this change caused deadlocks or other problems, one can disable it by setting the "jdt.compiler.useSingleThread" property to "true" 

E.g. passing the following as a VM argument when starting Eclipse:
  -Djdt.compiler.useSingleThread=true

Comment 8 David Audel

2008-04-29 10:04:48 EDT

Verified for 3.4M7 using I20080427-2000

Comment 9 Nirav Thaker

2008-06-25 10:20:21 EDT

(In reply to comment #8)
> Verified for 3.4M7 using I20080427-2000
> 

Can anyone point me where these changes were made? I'm interested in taking a look but couldn't find anything on this bug or in release notes.

Comment 10 Kent Johnson

2008-06-26 14:37:57 EDT

Nirav - take a look at the 2 classes;

org.eclipse.jdt.internal.compiler.ReadManager
org.eclipse.jdt.internal.compiler.ProcessTaskManager 

& where they attach to the Compiler.


If you need any more information, just let us know.