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

Yes — that's after a ton of Rust-centric optimisation. About 25% of the runtime is currently consumed with deallocating memory (there are a lot of heavily-nested data structures getting cleaned up), so there's definitely some more work to be done to reduce cloning.


what's the total running time? ms/sec/minutes/hours? is it heavy IO bound?


A few minutes.

It's not heavily IO-bound — it's mostly memory-bound (it's a type-checking tool for very large codebases).

Further (painful) optimisations will likely involve the use of arenas to prevent so many atomic de-allocations.




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

Search: