user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: update HACKING and TODO with a few items
Date: Sat, 21 Sep 2019 00:06:42 +0000	[thread overview]
Message-ID: <20190921000642.7290-1-e@80x24.org> (raw)

Inline::C seems alright, so we might use it more since it still
allows end users to quickly make changes.  Our performance on
rotational disks is also terrible, and could be improved...
---
 HACKING | 3 ++-
 TODO    | 8 +++-----
 2 files changed, 5 insertions(+), 6 deletions(-)

diff --git a/HACKING b/HACKING
index c2f4825c..f7cb92e9 100644
--- a/HACKING
+++ b/HACKING
@@ -40,7 +40,8 @@ the shiny new.
 Avoid relying on compiled modules too much.  Even if it is Free,
 compiled code makes packages more expensive to audit, build,
 distribute and verify.  public-inbox itself will only be implemented
-in scripting languages (currently Perl 5).
+in scripting languages (currently Perl 5) and optional JIT-compiled C
+(via Inline::C)
 
 Performance should be reasonably good for server administrators, too,
 and we will sacrifice features to achieve predictable performance.
diff --git a/TODO b/TODO
index 9f58342f..8f78d87d 100644
--- a/TODO
+++ b/TODO
@@ -5,7 +5,7 @@ performance, ease-of-setup, installation, maintainability, etc
 all need to be considered for everything we introduce)
 
 * general performance improvements, but without relying on
-  XS or compiled code any more than we currently do.
+  XS or pre-built modules any more than we currently do.
 
 * mailmap support (same as git) for remapping expired email addresses
 
@@ -101,10 +101,8 @@ all need to be considered for everything we introduce)
 * imperfect scraper importers for obfuscated list archives
   (e.g. obfuscated Mailman stuff, Google Groups, etc...)
 
-* support hooks, since low-level git-fast-import does not run them
-  https://public-inbox.org/meta/20190405174329.GA21472@chatter.qube.local/
-  (note: may not be needed since we do grokmirror manifest.js.gz, now)
-
 * consider using HTTP::Date instead of Date::Parse, since we need the
   former is capable of parsing RFC822-ish dates, used by Plack, and
   the latter is missing from OpenBSD and maybe other distros.
+
+* improve performance and avoid head-of-line blocking on slow storage
-- 
EW


             reply	other threads:[~2019-09-21  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21  0:06 Eric Wong [this message]
2019-09-21 22:40 ` libgmime experiences? (was: [PATCH] doc: update HACKING and TODO ...) Eric Wong
2019-11-16  2:50   ` Eric Wong

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20190921000642.7290-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.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).