Don't forget the cost of managing your one big server and the risk of having such single point of failure.
Related: https://brooker.co.za/blog/2024/06/04/scale.html
Readit Newsjoek1301 commented on Use One Big Server (2022) specbranch.com/posts/one-... · Posted by u/antov825
Normally this kind of thing would be absolutely ripe for abuse, but with the guardrails in place for the mainstream SOTA models, it might actually be okay. Maybe I'll be proven wrong.
joek1301 commented on A collection of quant riddles with answers puzzles.nigelcoldwell.co.... · Posted by u/alexmolas
For #14, some of us went a little nuts optimizing the dynamic programming solution down from months/OOM to milliseconds, and going past the original suggested problem size of a few hundred to a maximum problem size of 133 million: https://gwern.net/problem-14
I clicked your link, saw DP, and tabbed away to try and solve it myself first. (I also forgot to sample without replacement and wound up with $2.86.)
Delightful read!
joek1301 commented on How to keep lambda calculus simple hirrolot.github.io/posts/... · Posted by u/azhenley
What the hell is `:@:`? Cannot google that, and the GHC docs don't tell either.
It defines a new infix data constructor. So if `it` and `ct` are values of type `ITerm` and `CTerm` respectively, `it :@: ct` is a value of type `ITerm`. (It could have been written using a prefix operator like `ITerm`'s other data constructors.)