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.

Bug 244430 - NetBeans created system processes are very slow compared to real system processes
Summary: NetBeans created system processes are very slow compared to real system proce...
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.0.2
Hardware: Macintosh (x86) Mac OS X
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-12 01:03 UTC by asbachb
Modified: 2015-06-17 08:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NetBeans profile data during mvn clean package of ninja-3.1.4 (1.46 MB, application/octet-stream)
2014-05-12 01:03 UTC, asbachb
Details
build log netbeans (345.18 KB, text/rtf)
2014-10-30 13:31 UTC, asbachb
Details
build log terminal (1.02 MB, text/rtf)
2014-10-30 13:32 UTC, asbachb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description asbachb 2014-05-12 01:03:39 UTC
Created attachment 147222 [details]
NetBeans profile data during mvn clean package of ninja-3.1.4

#SUMMARY
I recognised some huge performance differences when NetBeans creates new system processes. For example and ordinary maven build or starting an application server like Wildfly.

#HOW TO REPRODUCE
1) git clone https://github.com/ninjaframework/ninja.git
2) git checkout ninja-3.1.4
3) mvn clean package

When using Terminal: approx. 42s
When using NetBeans: approx. 2:35s

#SAME BEHAVIOUR
When starting Wildfly AS the scenario is quite the same:

Starting using Terminal: approx. 4s
Starting using IDE: 21s
Comment 1 asbachb 2014-05-12 12:06:57 UTC
#ADDITIONAL INFORMATION

java -version
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)

Software  OS X 10.9.2 (13C1021)
Comment 2 Tomas Hurka 2014-05-16 13:42:43 UTC
Reassigning to project/maven to investigate what is going on.
Comment 3 asbachb 2014-05-16 23:18:22 UTC
After increasing the Memory via -Xmx2048m my runtime is about "2:06.862s"

I also recognized that after the invocation:

"cd /Users/asbachb/dev/extsrc/ninja-framework; JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home M2_HOME=/usr/local/Cellar/maven/3.1.1/libexec /usr/local/Cellar/maven/3.1.1/libexec/bin/mvn clean package"

It takes about 5 seconds until the process itself starts and "Scanning for projects..." appears.
Comment 4 asbachb 2014-10-30 13:31:05 UTC
Retested with 

NetBeans 8.0.1
Maven 3.2.3
Java 1.8u55

Terminal: approx. 39s
NetBeans: approx. 2m 5s

attached logs of terminal and NetBeans builds
Comment 5 asbachb 2014-10-30 13:31:52 UTC
Created attachment 150168 [details]
build log netbeans
Comment 6 asbachb 2014-10-30 13:32:24 UTC
Created attachment 150169 [details]
build log terminal
Comment 7 Tomas Stupka 2015-06-17 08:56:34 UTC
i wasn't able to reproduce with an current dev build Build 20150617-4d07287fa0b6

mvn clean package
cli: 40s
ide: 50s

mvn clean package -DskipTests 
cli: 18s
ide 21s

mvn clean instal
cli: 56s
ide: 1:04s

please take in count that the ide does some extra work and hence the slightly higher results

feel free to reopen in case this problem does still prevail with a current dev build
in such a case please attach an actual profiler snapshot

thanks