Newest at the top
| 2026-05-30 12:13:38 +0000 | merijn | (~merijn@62.45.136.136) (Ping timeout: 248 seconds) |
| 2026-05-30 12:12:07 +0000 | <int-e> | (but yeah I think it's best to treat it as pseudo-random) |
| 2026-05-30 12:12:04 +0000 | <tomsmeding> | :D |
| 2026-05-30 12:11:49 +0000 | <int-e> | tomsmeding: it's so annoyingly deterministic noise though ;) |
| 2026-05-30 12:11:02 +0000 | <tomsmeding> | I have a friend over though so this is the end of investigation from my side :p |
| 2026-05-30 12:10:52 +0000 | <tomsmeding> | int-e: interesting, I guess "GC" explains all the random noise that we're seeing? |
| 2026-05-30 12:09:10 +0000 | merijn | (~merijn@62.45.136.136) merijn |
| 2026-05-30 12:02:43 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2026-05-30 11:55:32 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 11:52:09 +0000 | tjbc | (~tjbc@user/fliife) (Ping timeout: 248 seconds) |
| 2026-05-30 11:46:34 +0000 | <int-e> | and you'll see, for example, that the :q triggers a final GC (presumably), and that the time that takes varies |
| 2026-05-30 11:45:33 +0000 | <int-e> | tomsmeding: well, one final thing: if you look at that script, you'll see that I have a function for producing the input. it's interesting to look at the graphs when uncommenting those two `sleep` commands... that separates the system calls nicely by the commands that trigger them. |
| 2026-05-30 11:44:56 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 261 seconds) |
| 2026-05-30 11:42:40 +0000 | Icy-Thought | (~user@user/icy-thought) icy-thought |
| 2026-05-30 11:42:31 +0000 | <int-e> | but let me dig myself out of this rabbit hole |
| 2026-05-30 11:42:25 +0000 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2026-05-30 11:39:42 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 11:39:07 +0000 | <int-e> | my whole glorious .ghci file has two lines: ":set -Wno-x-partial" and "let c n 0 = 1; c n k = c (n-1) (k-1) * n `div` k". |
| 2026-05-30 11:37:47 +0000 | califax_ | califax |
| 2026-05-30 11:37:47 +0000 | califax | (~califax@user/califx) (Ping timeout: 252 seconds) |
| 2026-05-30 11:36:11 +0000 | califax_ | (~califax@user/califx) califx |
| 2026-05-30 11:36:11 +0000 | <int-e> | and no, I can't explain why an empty .ghci triggers one less major GC here |
| 2026-05-30 11:35:21 +0000 | <int-e> | (obviously don't run that script blindly; it needs its own clean directory) |
| 2026-05-30 11:33:49 +0000 | <int-e> | tomsmeding: I think I'm wrong and we're really looking at GC times: https://int-e.eu/~bf3/tmp/ghci3.png (this is with 9.12.2 again, using https://paste.tomsmeding.com/ForwLizz ) |
| 2026-05-30 11:29:04 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds) |
| 2026-05-30 11:28:22 +0000 | Lord_of_Life_ | Lord_of_Life |
| 2026-05-30 11:25:53 +0000 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 269 seconds) |
| 2026-05-30 11:25:30 +0000 | Lord_of_Life_ | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2026-05-30 11:23:55 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 11:18:18 +0000 | <tomsmeding> | https://tomsmeding.com/vang/4hqRvJ/ghci9.14.png |
| 2026-05-30 11:17:42 +0000 | <tomsmeding> | and 9.14 is like 9.12 |
| 2026-05-30 11:17:08 +0000 | <tomsmeding> | ok that was still 9.8; with 9.12 the graphs are much different |
| 2026-05-30 11:13:21 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 267 seconds) |
| 2026-05-30 11:09:22 +0000 | <tomsmeding> | observation: none and ignore are not equivalent |
| 2026-05-30 11:08:50 +0000 | <tomsmeding> | https://paste.tomsmeding.com/vuwPAm3U https://tomsmeding.com/vang/z6j2PO/ghci4.png |
| 2026-05-30 11:08:10 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 11:02:48 +0000 | tremon | (~tremon@83-80-159-219.cable.dynamic.v4.ziggo.nl) (Remote host closed the connection) |
| 2026-05-30 11:01:28 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2026-05-30 11:00:42 +0000 | <int-e> | (but the full one *does* compile byte code because it defined a function) |
| 2026-05-30 11:00:21 +0000 | <int-e> | yup, empty was flawed, I didn't hide my main .ghci from ghci: https://int-e.eu/~bf3/tmp/ghci2.png puts the empty .ghci between ignore-dot-ghci and the tiny full one |
| 2026-05-30 10:58:01 +0000 | Inline | (~noOne@ipservice-092-208-182-236.092.208.pools.vodafone-ip.de) Inline |
| 2026-05-30 10:57:58 +0000 | <tomsmeding> | I'm testing with 9.8.4 here, I can try 9.12 |
| 2026-05-30 10:57:55 +0000 | <int-e> | I think my 'empty' case is flawed |
| 2026-05-30 10:57:45 +0000 | <int-e> | hmmmm |
| 2026-05-30 10:57:05 +0000 | <int-e> | tomsmeding: hmm, for me -ignore-dot-ghci comes out ahead (ghc-9.12.2): https://int-e.eu/~bf3/tmp/ghci1.png |
| 2026-05-30 10:56:45 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-30 10:55:37 +0000 | Guest43 | (~Guest43@p200300dcb74099005424e44ccbbb78bd.dip0.t-ipconnect.de) (Ping timeout: 245 seconds) |
| 2026-05-30 10:49:28 +0000 | dtman34 | (~dtman34@c-73-242-68-179.hsd1.mn.comcast.net) dtman34 |
| 2026-05-30 10:49:07 +0000 | dtman34 | (~dtman34@c-73-242-68-179.hsd1.mn.comcast.net) (Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in) |
| 2026-05-30 10:47:17 +0000 | <tomsmeding> | the number of syscalls is commensurate with what one would expect, but blue (no .ghci) and red (empty .ghci) are the other way round in runtime |
