Eclipse validating xml slow
The result is a simple, yet efficient JSHint Eclipse integration that validates the same bunch of *files in less than 15 seconds.This speedup could be achieved by exploiting the way Eclipse builds projects: It uses the same builder instance to visit all files of the project recursively.
Create fresh PHP Eclipse PDT installation and try to keep plugins to minimum. If you get crash out of perm space then increase in 64MB steps. -startup plugins/org.eclipse.equinox.launcher_1.1.0.v20100419--launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100322-1720 -product org.product --launcher. XXMax Perm Size 128M -showsplash org.eclipse.platform --launcher.Another good idea is to keep files like images, configs, xml data etc separately if you have a lot of them.Public folder with thousands of different files will slow eclipse down as well especially if they contain xml / js / css / html.Like JSLint, JSHint is written in Java Script, but can be run on the command line using tools like Rhino or Java Script Core.I tried JSHint on our codebase with good results using a shell script that runs it on top of Rhino.XXMax Perm Size 256m –launcher.default Action open File -vmargs -server -Dosgi.required Java Version=1.5 -Xmn128m -Xms1024m -Xmx1024m -Xss2m -XX: Perm Size=128m -XX: Max Perm Size=128m -XX: Use Parallel GC 4. Then set the Im Disk driver to auto-load at Command Prompt with administrative privileges (for example right-click, start as Administrator), type: sc config imdisk start= auto net start imdisk create a 200m ram disk as driver n by: imdisk -a -t vm -s 300m -m n: then you should format the ram disk manually.
Create a ram disk(virtual disk) on memory, and put your jdk on the ram disk. later ,if you would like to remove the ram disk, just run the command: imdisk -D -m n: 5.
You do not edit pear and zend libraries so put them out of the project folder.
Create some symlinks structure so that you use the library on in the development server but they are not in the eclipse project.
Unfortunately, checking all our 250 *files keeps my machine busy for 5 minutes and 40 seconds and effectively turns it into a fan heater.
This is not because JSHint itself is so demanding, but because for every file, a JVM has to be started, Rhino has to be loaded, then Rhino has to parse and load the JSHint Java Script library, and then finally, jshint can parse and validate the source file.
We use the JSEclipse plug-in for Java Script editing which detects some, but not many Java Script problems.