unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: February update on the Guile guix-daemon
Date: Sat, 24 Feb 2024 17:48:02 +0100	[thread overview]
Message-ID: <87ttlx6c71.fsf@gnu.org> (raw)
In-Reply-To: <87cysqn2ko.fsf@cbaines.net> (Christopher Baines's message of "Tue, 20 Feb 2024 19:53:43 +0000")

Hello!

Thanks for the update!

Christopher Baines <mail@cbaines.net> skribis:

>  - Then there's the big areas to work on next:
>
>    - I think I'm going to need to use thread pools for SQLite operations
>      in the daemon, as the build coordinator does.

I think we should refrain from using POSIX threads directly and instead
use Fibers to its full extent.  In this case, I’d use a resource pool as
done in Cuirass (and in the Coordinator too, no? maybe that’s what you
meant?).

>    - There's the low level work of setting up the build environment, the
>      work on the guile-daemon branch helps a lot with this, but as
>      pointed out by Ludo, there might be some issues with fork and
>      similar operations in a Guile program using threads.

Right.  I think one of the things we discussed in Brussels is that,
since SQLite operations might block for a while, the daemon will have to
be multithreaded.  Which means no fork/clone, which in turn probably
means delegating forking/cloning to a separate helper process.  (That’s
also what bubblewrap does, IIUC.)

>    - While I've implemented some of the server side protocol used by the
>      daemon, I'd like to extract that code in to a module so that it's
>      not wrapped up inside the daemon script

Wo0t!

Cheers,
Ludo’.


  reply	other threads:[~2024-02-24 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 19:53 February update on the Guile guix-daemon Christopher Baines
2024-02-24 16:48 ` Ludovic Courtès [this message]
2024-02-26 11:05   ` Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttlx6c71.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).