This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Internally spawned processes don't carry the -J-client flag from invoker command line | ||
---|---|---|---|
Product: | installer | Reporter: | esmithbss <esmithbss> |
Component: | Code | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
esmithbss
2011-01-31 16:48:32 UTC
How many java child processes are launched during the installation? Installing the full build starts several java processes testing JDK installation and several processes at the end. How does this make the installation slower? Are you trying to say that the installation hangs while it's running the simple TestJVM? Please attach the installer output, so i can see where it hangs, thanks Yes, the TestJVM process is extremely slow on my machine. Even my big machine. What happens is the default invocation of Java assumes -server since I have 2 cores and Windows virtualizes them to 4 so it looks like it's a massive quad core box. But java -server is excessively slow when performing many tasks (I don't know why, but it is). That is compounded by the TestJVM's being serialized (I have a few installed because I support so many things). So some parallel processing and -client will speed things up tremendously. I'll attach an install log once that machine finishes it's current processing. esmithbss says: I'll attach an install log once that machine finishes it's current processing. |