user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PUSHED 0/2] relnotes and some notes about the future
Date: Fri, 17 Apr 2020 09:11:01 +0000	[thread overview]
Message-ID: <20200417091103.22488-1-e@yhbt.net> (raw)

So I've got some vague ideas of what 1.5 will entail...

I'm still disatisfied with memory consumption and performance;
so more on that.  Maybe some more optional Inline::C, but
ease-of-installation still must be taken into account.

I started writing Documentation/technical/data_structures.txt a
some time ago and realized we could reduce, eliminate and reuse
some data structures.  That would allow us to document less
things, reduce cognitive load on hackers, AND save some RAM :>

Another place that bothers me is we build up big, per-message
memory buffers for HTML/Atom feeds.  Since most HTTP requests
are compressed anyways, I've been slowing moving towards
buffering directly to gzip, allowing our internal memory
representation to be compressed.  Though it may not help a lot
because deflate contexts take several dozen kilobytes of RAM.
Still, that allows us to avoid Plack::Middleware::Deflater and
the memory-wasting closures it imposes.  And one less
dependency in the INSTALL file, too.

Eric Wong (2):
  public-inbox 1.4.0
  doc: update 1.4.0 relnotes with date, start 1.5.0

 Documentation/RelNotes/v1.4.0.eml | 29 ++++++++++++++++++++++-------
 Documentation/RelNotes/v1.5.0.eml | 13 +++++++++++++
 MANIFEST                          |  1 +
 Makefile.PL                       |  4 ++--
 4 files changed, 38 insertions(+), 9 deletions(-)
 create mode 100644 Documentation/RelNotes/v1.5.0.eml


             reply	other threads:[~2020-04-17  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17  9:11 Eric Wong [this message]
2020-04-17  9:11 ` [PATCH 1/2] public-inbox 1.4.0 Eric Wong
2020-04-17  9:11 ` [PATCH 2/2] doc: update 1.4.0 relnotes with date, start 1.5.0 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=20200417091103.22488-1-e@yhbt.net \
    --to=e@yhbt.net \
    --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).