|
|
|
I committed a fix that modifies ListNode to use an ArrayList rather than an array it grows one element at a time. This actually appeared to improve Rails startup by a couple seconds, and once started there was no appreciable difference in memory consumption. That brings the run time for 100k.rb down to a few seconds. There are other bottlenecks we should look into, however, so we'll leave this open to remind us of an ugly parser edge case with still-too-slow performance.
Reopened the issue per Charlie's comments.
I'm going to mark this fixed, since we have put the ArrayList in place and it solved the vast bulk of performance problems. There should be other bugs file for specific perf problems in parsing, or for general parsing perf improvements.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||
For me, the run time is down to 7 secs from 30-45 secs, so I consider this result to be OK, given this is a very pathological case.