http://gwt-code-reviews.appspot.com/1425805/diff/3002/user/src/com/google/web/bindery/requestfactory/server/RequestFactoryJarExtractor.java File user/src/com/google/web/bindery/requestfactory/server/RequestFactoryJarExtractor.java (right):
http://gwt-code-reviews.appspot.com/1425805/diff/3002/user/src/com/google/web/bindery/requestfactory/server/RequestFactoryJarExtractor.java#newcode760 user/src/com/google/web/bindery/requestfactory/server/RequestFactoryJarExtractor.java:760: int numThreads = Math.min(MAX_THREADS, Runtime.getRuntime().availableProcessors()); On 2011/04/20 19:25:21, bobv wrote:
Why limit to 4?
The real reason was to just keep a way to throttle the number of threads. Do you prefer another limit or would prefer an unlimited number of threads? Running several instances of this job with 4 threads on an 8 core box runs in zero seconds (reported by ant) on my box. I'm not sure more threads are going to speed it up any more. http://gwt-code-reviews.appspot.com/1425805/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
