From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Change of Hashsize in acid (slow startup on netsurf)
Date: Tue, 5 Jan 2021 23:39:05 +0100 [thread overview]
Message-ID: <CAFSF3XPCtSnqqv9jB+m+q6s-rTK=SazWRQYaVSjQac-S7Oobhw@mail.gmail.com> (raw)
In-Reply-To: <13671796-C244-493E-905C-15F3DDE1693B@stanleylieber.com>
i mean, somehow the 9front mailing list software seems to be
complaining about gmail...
On 1/5/21, Stanley Lieber <sl@stanleylieber.com> wrote:
> On January 5, 2021 4:10:19 PM EST, hiro <23hiro@gmail.com> wrote:
>>i did not manage to quote the relevant part:
>>
>>Authentication-Results: mx.google.com;
>> dkim=neutral (body hash did not verify) header.i=@gmail.com
>>header.s=20161025 header.b=frcOH6pW;
>> spf=pass (google.com: domain of 9front-bounces@1ess.inri.net
>>designates 216.126.196.35 as permitted sender)
>>smtp.mailfrom=9front-bounces@1ess.inri.net;
>> dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
>>Received: from mail-vk1-f180.google.com ([209.85.221.180]) by 1ess; Tue
>> Jan
>>
>>the old server, ewsd seems to have done the same, but somehow gmail
>>didn't take it serious (perhaps people have trained gmail well enough
>>by manually pressing NOT SPAM).
>>
>>On 1/5/21, hiro <23hiro@gmail.com> wrote:
>>> the 9front mailing list seems to be making a weird subdomain
>>> quarantine decision:
>>>
>>> Authentication-Results: mx.google.com;
>>> dkim=neutral (body hash did not verify) header.i=@gmail.com
>>> header.s=20161025 header.b=frcOH6pW;
>>> spf=pass (google.com: domain of 9front-bounces@1ess.inri.net
>>> designates 216.126.196.35 as permitted sender)
>>> smtp.mailfrom=9front-bounces@1ess.inri.net;
>>> dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
>>>
>>> but the from header does not specify a subdomine, so quarantine should
>>> not
>>> apply
>>>
>>> ---------- Forwarded message ----------
>>> From: Jonas Amoson <jonas.amoson@gmail.com>
>>> Date: Tue, 5 Jan 2021 14:10:09 +0200
>>> Subject: [9front] Change of Hashsize in acid (slow startup on netsurf)
>>> To: 9front@9front.org
>>>
>>> It is slow to debug netsurf with acid, as it takes a long time to load
>>> all the symbols from the binary. It is the process of checking if a
>>> symbol has been encountered before, the function unique(), that makes
>>> the loading slow.
>>>
>>> Changing Hashsize from 128 to 32768 in acid takes down the loading
>>> time from 4 minutes to 8 seconds for me (45 times faster). Philippe
>>> reported a similar speed increase (30x from 15 min to 30 sec).
>>>
>>> I don't know if it is desirable to change the hashsize in the 9front
>>> repo, as it probably is only netsurf that has so many symbols to load,
>>> that it matters. But it might be that it doesn't harm anything either.
>>>
>>> /Jonas
>>>
>>
>
> i failed to get the ptr record updated until earlier today. hopefully gmail
> will stop complaining once it propagates.
>
> sl
>
next prev parent reply other threads:[~2021-01-05 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 12:10 Jonas Amoson
2021-01-05 21:03 ` Fwd: " hiro
2021-01-05 21:10 ` hiro
2021-01-05 22:16 ` Stanley Lieber
2021-01-05 22:39 ` hiro [this message]
2021-01-05 23:01 ` Stanley Lieber
2021-01-06 9:07 ` hiro
2021-01-06 15:23 ` Stanley Lieber
2021-01-06 16:23 ` hiro
2021-01-05 21:59 ` ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFSF3XPCtSnqqv9jB+m+q6s-rTK=SazWRQYaVSjQac-S7Oobhw@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).