Has anyone looked at seq2sparse performance in recent memory? I'm wondering if anyone has any ideas for improving it. Based on my reading of the code, it likely is slowly due to the sheer number of steps it has to do, but I'm hoping there are some other cheaper wins hiding in there. (I am aware that I can speed things up by chopping off more terms, etc.)
-------------------------------------------- Grant Ingersoll | @gsingers http://www.lucidworks.com
