I'm disappointed, but in a good way. I thought jLinq was 'good enough'. It performed the way it should and that was good enough for me. These results tell a much different story.
jLinq probably performs well in typical scenarios, whereas these benchmarks are for medium to large arrays queried thousands of times. I've used it in several projects with great results.
Regardless, jLinq clearly performs slower than it should. Reviewing the jLinq code I can think of a few potential pain points.
- The entire jLinq object and all of the commands are generated each time a query is started. jLinq there should be a way to cache a standard jLinq object and only rebuild it when needed.
- jLinq uses a lot of
I appreciate Dan showing these results to me. Sharing your code with others is a great way to get feedback about what you write... even if it is a kick in the butt.
August 4, 2010
jLinq Performance Analyzed
Post titled "jLinq Performance Analyzed"