Re:Professor Frisby's mostly adequate guide to functional pr...
by th0114nd on Sunday March 22, 2020 @09:41PM
(#22660501)
I worked as a Haskell developer for a year and a half. The best productivity boost I had was switching to compiling on an EC2 instance. I saved battery, sped up compiles with greater parallelism than my XPS had cores for, and didn’t have to worry about cleaning up ~/.stack
[ Parent
| on HN ]
Re:Professor Frisby's mostly adequate guide to functional pr...
by tome on Monday March 23, 2020 @06:27AM
(#22662600)
Could you give a short explanation or link to a write up? Which size of EC2 instance works well for compiling Haskell? Does the EC2 live only for the duration of the compile, or permanently? If only for the duration, how do you deal with persisting the installed libraries to disk? Thanks!
Re:Professor Frisby's mostly adequate guide to functional pr...
by th0114nd on Tuesday March 24, 2020 @02:49AM
(#22672603)
I can’t recall exactly, I want to say 16 vCPUs and 64GB. How well a project can make use of the cores depends on how wide your dependency graph is vs how tall, as the unit of parallelism is a package.
The EC2 instance was on continuously, and I would ssh+tmux in. You could probably replace this with a server plugged in under your desk, depending on how much you trade off operational costs and capital costs.
More often than not I wanted passing tests to send something for review. If I needed an artifact, I would publish a docket image on an internal registry.
Re:Professor Frisby's mostly adequate guide to functional pr...
by awinter-py on Sunday March 22, 2020 @09:45PM
(#22660517)
wait do I need to worry about cleaning up ~/.stack