2026/06/25

Newest at the top

2026-06-25 04:14:01 +0000Enigmagic(~Enigmagic@user/Enigmagic) Enigmagic
2026-06-25 04:11:25 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2026-06-25 04:07:44 +0000humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-06-25 04:07:14 +0000karenw(~karenw@user/karenw) karenw
2026-06-25 04:07:00 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 04:03:06 +0000michalz(~michalz@185.246.207.197)
2026-06-25 04:02:15 +0000Enigmagic(~Enigmagic@user/Enigmagic) (Ping timeout: 245 seconds)
2026-06-25 03:58:02 +0000Enigmagic(~Enigmagic@user/Enigmagic) Enigmagic
2026-06-25 03:56:21 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-06-25 03:51:37 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 03:47:58 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2026-06-25 03:46:14 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: Leaving)
2026-06-25 03:45:14 +0000slack1256(~slack1256@2803:c600:5111:c9d8:89ea:2350:54ae:a3d) (Remote host closed the connection)
2026-06-25 03:44:09 +0000Enigmagic(~Enigmagic@user/Enigmagic) (Ping timeout: 248 seconds)
2026-06-25 03:43:00 +0000slack1256(~slack1256@2803:c600:5111:c9d8:89ea:2350:54ae:a3d) slack1256
2026-06-25 03:41:39 +0000slack1256(~slack1256@2803:c600:5111:c9d8:89ea:2350:54ae:a3d) ()
2026-06-25 03:40:45 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)
2026-06-25 03:37:30 +0000Enigmagic(~Enigmagic@user/Enigmagic) Enigmagic
2026-06-25 03:36:15 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 03:25:08 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-06-25 03:25:06 +0000machinedgod(~machinedg@d108-173-95-19.abhsia.telus.net) (Ping timeout: 248 seconds)
2026-06-25 03:20:53 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 03:11:01 +0000fgarcia(~lei@user/fgarcia) fgarcia
2026-06-25 03:10:40 +0000 <slack1256> This is interesting
2026-06-25 03:10:37 +0000 <slack1256> https://jhhuh.github.io/ghc-fastboot/ghc-compact-regions-and-runtime-limitations/
2026-06-25 03:10:35 +0000 <slack1256> The long term state is not static.
2026-06-25 03:09:52 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2026-06-25 03:09:01 +0000vgtw(~vgtw@user/vgtw) vgtw
2026-06-25 03:08:34 +0000vgtw(~vgtw@user/vgtw) (Ping timeout: 276 seconds)
2026-06-25 03:06:47 +0000 <EvanR> slack1256, if the long term state is static compact regions might work
2026-06-25 03:02:50 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 02:58:24 +0000 <slack1256> Alternatively, having options to reduce RTS statup cost (memory mainly) would help a lot. launching 5 binaries usually start at arround 32MiB for the startup cost.
2026-06-25 02:57:00 +0000leppard(~noOne@ipservice-092-209-218-237.092.209.pools.vodafone-ip.de) (Ping timeout: 246 seconds)
2026-06-25 02:56:41 +0000emmanuelux(~em@user/emmanuelux) (Quit: bye)
2026-06-25 02:54:28 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2026-06-25 02:53:54 +0000 <geekosaur> you would otherwise need multiple heaps, each with its own gc, and ghc's rts doesn't support that
2026-06-25 02:52:40 +0000 <geekosaur> ghc at least doesn't give you any options there, unless the long term state is also not changing in which case you might like compact regions
2026-06-25 02:52:19 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-06-25 02:51:42 +0000wickedjargon(~user@64.114.24.74) (Read error: Connection reset by peer)
2026-06-25 02:48:24 +0000 <slack1256> the runtime is basically non existent and I am not punished by breaking the binaries. What other options should I consider? I would like to reuse the haskell RTS but the parameters for sections of the programs should be different.
2026-06-25 02:48:24 +0000 <slack1256> At <work> we use multiple binaries interacting via protobuf to solve a business problem. They are only separated because the GC parameters on the RTS should be different for each. One of these hold long term state (non moving) while the others would do better with parallel GC and so on. The major problem with this setup is that each binary carries its own RTS and that is a constant memory use. If these binaries were made from C
2026-06-25 02:47:28 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 02:44:51 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Ping timeout: 252 seconds)
2026-06-25 02:44:51 +0000vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 252 seconds)
2026-06-25 02:43:05 +0000slack1256(~slack1256@2803:c600:5111:c9d8:89ea:2350:54ae:a3d) slack1256
2026-06-25 02:41:25 +0000Enigmagic(~Enigmagic@user/Enigmagic) (Ping timeout: 245 seconds)
2026-06-25 02:37:04 +0000Enigmagic(~Enigmagic@user/Enigmagic) Enigmagic
2026-06-25 02:36:25 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-06-25 02:32:05 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-06-25 02:31:04 +0000td_(~td@i53870935.versanet.de) td_