From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: sample robots.txt to reduce WWW load
Date: Mon, 8 Apr 2024 23:58:31 +0000 [thread overview]
Message-ID: <20240408235831.M464581@dcvr> (raw)
In-Reply-To: <20240403223144.M651128@dcvr>
Eric Wong <e@80x24.org> wrote:
> I've unleashed the bots again and let them run rampant on the
> https://80x24.org/lore/ HTML pages. Will need to add malloc
> tracing on my own to generate reproducible results to prove it's
> worth adding to glibc malloc...
Unfortunately, mwrap w/ tracing is expensive enough to affect
memory use: slower request/response processing due to slower
malloc means larger queues build up.
Going to have to figure out lower-overhead tracing mechanisms if
I actually want to prove size classes work to reduce
fragmentation....
prev parent reply other threads:[~2024-04-08 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 13:21 sample robots.txt to reduce WWW load Eric Wong
2024-04-03 20:58 ` Konstantin Ryabitsev
2024-04-03 22:31 ` Eric Wong
2024-04-08 23:58 ` Eric Wong [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://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=20240408235831.M464581@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.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.
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).