Severe performance drop with jshint 1.1.0 #958

Closed
ralfstx opened this Issue Mar 23, 2013 · 3 comments

Projects

None yet

3 participants

@ralfstx

Checking many files using rhino takes more than 6 times longer than with version r12. This performance drop renders jshint 1.1.0 almost unusable in an IDE, see eclipsesource/jshint-eclipse#43.

$ time rhino jshint-rhino-r12.js `find git/jshint -name '*.js > problems

real    0m4.536s
user    0m8.273s
sys     0m0.104s

$ time rhino jshint-rhino-1.1.0.js `find git/jshint -name '*.js'` > problems

real    0m36.680s
user    0m49.119s
sys     0m0.200s
@valueof
JSHint member

I'll try to profile it but can't promise anything. Node is the priority platform for JSHint.

@levsa

I've noticed this as well. I'm using rhino version with gradle-js-plugin. Build time for a module with ~1100 files is 11 minutes with latest jshint-rhino (-opt 9 flag to rhino), but around 30s with jshint-rhino-r12.

@valueof
JSHint member

It's probably because browserify evals everything.

@valueof valueof added a commit that closed this issue Apr 8, 2013
@valueof valueof Upgrade Browserify to 2.12.0
This should improve performance on Rhino and resolve EventEmitter
leaks.

Closes GH-983.
Closes GH-958.
Closes GH-931.
Closes GH-889.
Affects GH-987.
f2843c5
@valueof valueof closed this in f2843c5 Apr 8, 2013
@jugglinmike jugglinmike added a commit to jugglinmike/jshint that referenced this issue Oct 21, 2014
@valueof valueof Upgrade Browserify to 2.12.0
This should improve performance on Rhino and resolve EventEmitter
leaks.

Closes GH-983.
Closes GH-958.
Closes GH-931.
Closes GH-889.
Affects GH-987.
d54e023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment