!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

415 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.139 Servers

Load older messages


SenderMessageTime
28 Jul 2025
@jade_:matrix.orgjade_* I concur on your suspicion on QoS being involved, since Kate actually also mentioned this a year ago iirc00:11:14
@emilazy:matrix.orgemily if it is priority inversion with the daemon then a quick fix may be as simple as ensuring the daemon re-execs itself with the posix_spawn API to set utility QoS class 00:12:37
@emilazy:matrix.orgemilyI also suspect something about logging could be very slow00:12:53
@jade_:matrix.orgjade_is there a way to get the task policy of a job?00:13:01
@jade_:matrix.orgjade_this is DEFINITELY true00:13:08
@jade_:matrix.orgjade_the logging in lix is blocking on the daemon00:13:15
@jade_:matrix.orgjade_ which is totally fucked and we can't really fix it in the current protocol, not easily at least 00:13:33
@jade_:matrix.orgjade_well, maybe we could00:13:42
@jade_:matrix.orgjade_we would just have to dispatch "logging" to a separate task than "dealing with proto"00:14:01
@jade_:matrix.orgjade_but it's super fragile00:14:04
@jade_:matrix.orgjade_known perf problem :(00:14:23
@emilazy:matrix.orgemilynot sure00:14:57
@jade_:matrix.orgjade_https://git.lix.systems/lix-project/lix/issues/717 here's the last time qos was mentioned and i filed a bug00:15:16
@jade_:matrix.orgjade_i would suspect it might be in either activity monitor, some xcode thing, or native ps00:15:48
@emilazy:matrix.orgemilywhoever led to that bug report must be super smart :D00:15:51
@emilazy:matrix.orgemilyI think it's not in Activity Monitor sadly00:16:09
@jade_:matrix.orgjade_ sudo powermetrics --show-process-qos --samplers tasks -n 1 | head -n 30 00:16:12
@emilazy:matrix.orgemilyhttps://developer.apple.com/library/archive/documentation/Performance/Conceptual/power_efficiency_guidelines_osx/PrioritizeWorkAtTheTaskLevel.html#//apple_ref/doc/uid/TP40013929-CH35-SW1000:16:18
@emilazy:matrix.orgemilyyeah00:16:24
@jade_:matrix.orgjade_copied directly out of the bazel thing00:16:25
@jade_:matrix.orgjade_https://git.lix.systems/lix-project/lix/issues/935 here filed another issue with the intent of the fault being written down00:20:28
@emilazy:matrix.orgemilylosing events sounds really bad for build logs00:20:59
@jade_:matrix.orgjade_agreed00:21:14
@emilazy:matrix.orgemilyespecially since a big Hydra farm spends most of its time with builders under intense load00:21:19
@emilazy:matrix.orgemily(well… ideally)00:21:24
@jade_:matrix.orgjade_ backpressure is probably the correct choice here, but it does mean that theres a correct amount of blocking for logs... 00:21:38
@jade_:matrix.orgjade_just not the amount we have00:21:47
@jade_:matrix.orgjade_we also do blocking syscalls on every log line lol00:22:09
@emilazy:matrix.orgemily I think it's already true, absent Nix, that make >/dev/null is faster than make 00:22:20
@emilazy:matrix.orgemilyIIRC Ninja might do smart stuff to mitigate that00:22:29

Show newer messages


Back to Room ListRoom Version: 10