unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <mulei@gnu.org>
To: Nala Ginrut <mulei@gnu.org>
Cc: Guile User <guile-user@gnu.org>, gnu-prog-discuss@gnu.org
Subject: Re: [BLOG] Demystify GNU Artanis service deployment in product environment
Date: Mon, 30 Dec 2024 16:17:57 +0900	[thread overview]
Message-ID: <8734i51vuj.fsf@gnu.org> (raw)
In-Reply-To: <87frm7253i.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]


We're tested the same benchmark on ARM64, it seems the performance is obviously
better than Intel, even after Linux Kernel Vaccine was enabled.

https://artanis.dev/blog/demystify-artanis-deployment-2.html

Best regards.


Nala Ginrut <mulei@gnu.org> writes:

> [[PGP Signed Part:Undecided]]
>
> Hi folks!
> You may want to read this post if you're any of these:
>
> 1. Want to know the best practice to deploy GNU Artanis web service in
> product environment.
>
> 2. If you care about sovereignty, this is best practice to deploy
> general web service of HardenedLinux community.
>
> 3. Interested in Linux Kernel Vaccine, in this full of APT (Advanced
> Persistent Threat) era. I think the runtime protection under GNU/Linux
> should be a new normal, e.g, VED full version, PaX/GRsecurity, etc...
>
> Here's the link:
> https://artanis.dev/blog/demystify-artanis-deployment.html
>
> Best regards.


--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
Fingerprint F53B 4C56 95B5 E4D5 6093 4324 8469 6772 846A 0058

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2024-12-30  7:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-28 15:25 [BLOG] Demystify GNU Artanis service deployment in product environment Nala Ginrut
2024-12-30  7:17 ` Nala Ginrut [this message]

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=8734i51vuj.fsf@gnu.org \
    --to=mulei@gnu.org \
    --cc=gnu-prog-discuss@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).