- Racket's IO system has been refactored to improve performance
and simplify internal design.
A huge thanks to everybody who worked on Racket.
IO improvements will surely make everybody’s life a little better in my team and the whole studio. We’re relying on large (200MB text files), and numerous (in the 100,000’s) file reads and writes daily. We’re converting shell scripts to Racket and I recon it’s hard to beat some GNU command’s optimizations. I have been tempted to try Rust but a) it’s not guaranteed to perform better for pure IO, and b) I’d rather code it directly in macro-asm if it meant better speed. But so far, Racket’s performance has been more than adequate for our tasks, and thanks to this I can do it all in Racket. That puts a big, gleeful smile on my face.
--
You received this message because you are subscribed to the Google Groups "Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CABNTSaEotkhQ_yK8n60fkFgkOmULX061eoj-LmDfhSBopA4h1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
I am also keen to know the IO perf optimization results in real world.Dexter, if possible can you give us some approximate throughput or latency numbers when you switch to v7.3
--
You received this message because you are subscribed to the Google Groups "Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/a2edb6b8-e792-42be-bfc9-63e78ef38e95%40googlegroups.com.