Improve Compile Performance

[wied03]

Since Hike caches the directory structure, construct a singleton Opal::PathReader.new instance and initialize every builder with it so that it's reused for multiple files. Might speed up compilation time. Might want to do programmatic benchmarks before/after.

[wied03]

Added some benchmarks in the brady/performance/hike branch. Trying to share a PathReader actually made things significantly worse though.

1.0.6

Starting benchmark for webpack to compile 200 files
              user     system      total        real
Run 0     0.000000   0.000000   6.760000 (  7.231685)
Run 1     0.000000   0.000000   6.710000 (  7.181848)
Run 2     0.000000   0.000000   6.980000 (  7.435301)


hike branch at ref 72076e992d5d675980536118d77cbf5d25409f07
Starting benchmark for webpack to compile 200 files
              user     system      total        real
Run 0     0.000000   0.000000   8.810000 (  9.412822)
Run 1     0.000000   0.000000   8.690000 (  9.278420)
Run 2     0.000000   0.000000   8.810000 (  9.398905)

With a shared PathReader:

Starting benchmark for webpack to compile 200 files
              user     system      total        real
Run 0     0.000000   0.000000  28.130000 ( 28.751145)
Run 1     0.000000   0.000000  28.700000 ( 29.311728)
Run 2     0.000000   0.000000  26.880000 ( 27.488145)

@cj - Does the 1.6-> 2nd results above match what you've seen? It sounds about right (29% slower)

[wied03]

@cj - I think the next step is probably to use the Node profiler rather than me guessing again.