Tip 1:
I find at sites with aggressive network virus scanners, the speed of JDeveloper on Windows is hindered by the virus scanner inspecting all the JAR files and other files on your local machine during normal JDeveloper r/w to the filesystem. As you can appreciate a JAR file is a zipped file, so the virus scanner has to unzip the JAR to scan for viruses, which is a double speed whammy (technical term for sloooooow).
From experience a version of McAfee disk-hog was 1 culprit, but luckily you can turn the scanner off for certain types of files (eg. JARs) or subdirectories (eg. the JDev install directory or your project directory).
Source:http://one-size-doesnt-fit-all.blogspot.in/2007/01/making-jdeveloper-faster-another-tip.html
I find at sites with aggressive network virus scanners, the speed of JDeveloper on Windows is hindered by the virus scanner inspecting all the JAR files and other files on your local machine during normal JDeveloper r/w to the filesystem. As you can appreciate a JAR file is a zipped file, so the virus scanner has to unzip the JAR to scan for viruses, which is a double speed whammy (technical term for sloooooow).
From experience a version of McAfee disk-hog was 1 culprit, but luckily you can turn the scanner off for certain types of files (eg. JARs) or subdirectories (eg. the JDev install directory or your project directory).
Source:http://one-size-doesnt-fit-all.blogspot.in/2007/01/making-jdeveloper-faster-another-tip.html
