public inbox for nncp-devel@lists.cypherpunks.ru
Atom feed
From: John Goerzen <jgoerzen@complete•org>
To: Sergey Matveev <stargrave@stargrave•org>
Cc: nncp-devel@lists.cypherpunks.ru
Subject: Re: Efficiency of caller/toss
Date: Fri, 20 Aug 2021 14:19:54 -0500 [thread overview]
Message-ID: <87zgtbudnp.fsf@complete.org> (raw)
In-Reply-To: <YR+DwavuZHd7wF6R@stargrave.org>
On Fri, Aug 20 2021, Sergey Matveev wrote:
> Parametrizing those timeouts, sleep times of course can be done
> and
> moved to configuration file. It will be tradeoff between even
> delays
> (how fast we react on new packets appearance) and CPU time. But
> at first
> I think I should look about possibly existing to use
> epoll/inotify/kqueue
> solution for Go, that will eliminate expensive regular
> syscalling at all.
> And of course leaving current while+sleep+dir-scan algorithm as
> a fallback
> for unsupported systems (kqueue/epoll are OS-specific).
Ah, if Go has a generic library for that, that would be fantastic.
Could be used in call, caller, daemon, and toss, I would imagine.
I do think sometimes about the overhead of the periodic scans on a
server that can often have nearly 10,000 files in the spool dir.
I'm probably overthinking it, as it's almost certainly cached and
most of those are .seen files that stick around for reasons I
understand (or .hdr ones that seem to stick around mysteriously
sometimes).
John
next prev parent reply other threads:[~2021-08-20 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 13:56 Efficiency of caller/toss John Goerzen
2021-08-18 18:14 ` Sergey Matveev
2021-08-18 19:20 ` John Goerzen
2021-08-18 19:29 ` Sergey Matveev
2021-08-20 2:24 ` John Goerzen
2021-08-20 10:28 ` Sergey Matveev
2021-08-20 19:19 ` John Goerzen [this message]
2021-08-21 18:38 ` Sergey Matveev
2021-08-23 14:10 ` Sergey Matveev
2021-09-02 9:06 ` Sergey Matveev
2021-09-02 13:07 ` John Goerzen
2021-09-02 13:34 ` Sergey Matveev
2021-08-20 10:23 ` Sergey Matveev