From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Announcement stis-engine
Date: Sat, 14 Aug 2021 06:09:38 +0200 [thread overview]
Message-ID: <CAGua6m3qn7pRdAHuEjq=LY_RtR+MJzEcgxF5nLjJht2BGucd6w@mail.gmail.com> (raw)
In-Reply-To: <CAGua6m3_49AR6vtUb3OFmyjUnHWy142oyfOsAFpuVv=qRM-3SQ@mail.gmail.com>
Okej the system starts to shape up. After some intensive hacking I managed
to make a toolbox for piping binary and scheme streams.
Currently it can pipe a list of 1000 000 elements typically around 1-4s.
see https://gitlab.com/tampe/stis-engine
On Sun, Aug 8, 2021 at 10:27 PM Stefan Israelsson Tampe <
stefan.itampe@gmail.com> wrote:
> I will start the development of stis-engine that is based on fibers and
> will experiment with applications that separate into different network
> components.
>
> Among things I plan to add serializers, deserializers, zipping and zero mq
> networking that works
> with fibers. E.g. we will stream things with fiber pipelines, use non
> blocking zero mq calls, avoid
> allocating large bytevectors, and use as little stack as possible in the
> code.
>
> This code depends on stis-data and optionally guile-persists
>
> References:
> https://gitlab.com/tampe/stis-engine
> https://gitlab.com/tampe/guile-persist
> https://gitlab.com/tampe/stis-data/
>
next prev parent reply other threads:[~2021-08-14 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 20:27 Announcement stis-engine Stefan Israelsson Tampe
2021-08-14 4:09 ` Stefan Israelsson Tampe [this message]
[not found] ` <c8cec86b-0c32-ce1d-106c-367f2ed7bf6e@posteo.de>
[not found] ` <CAGua6m1-vUgEk18Zb7cUw-Rp5kAz+Rg=LDF+0c26JBMghC2-zQ@mail.gmail.com>
2021-08-18 23:37 ` Stefan Israelsson Tampe
2021-08-23 17:31 ` Stefan Israelsson Tampe
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGua6m3qn7pRdAHuEjq=LY_RtR+MJzEcgxF5nLjJht2BGucd6w@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
/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.
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).