Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Added some benchmarking to show how fast it is:

Here is a benchmark comparing it to [Repomix][1] serializing the Next.js project:

      time yek
      Executed in    5.19 secs    fish           external
         usr time    2.85 secs   54.00 micros    2.85 secs
         sys time    6.31 secs  629.00 micros    6.31 secs



      time repomix
      Executed in   22.24 mins    fish           external
         usr time   21.99 mins    0.18 millis   21.99 mins
         sys time    0.23 mins    1.72 millis    0.23 mins


yek is 230x faster than repomix

[1] https://github.com/jxnl/repomix



Maybe I don't understand the usecase but I'm curious why speed matters given that LLMs are so slow (?)


22 minutes for a medium-sized repo is probably slow enough to optimize.


However for these large size repositories. I'm not sure that you fit in the effective context window. I know that there is option to limit the token but then this would be your realistic limit.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: