From: Jonathan Wakely <email@example.com>
To: "François Dumont" <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>,
Subject: Re: [PATCH] Enhance _Hashtable for range insertion 0/5
Date: Mon, 27 Jun 2022 17:18:40 +0100 [thread overview]
Message-ID: <CACb0b4mSsy7xJbCM7qgn2NT84VFCzr7ex26eCKNs3aB=RYc2hw@mail.gmail.com> (raw)
On Sun, 26 Jun 2022 at 21:06, François Dumont <email@example.com> wrote:
> I knew you were going to ask for it but was to impatient to propose
> those patches to wait anymore.
Heh, OK :-)
I've started reviewing them, but I thought I'd ask that question first.
> Attached you'll find what I start to work on. But I am quite
> disappointed by the results. At least it's showing that results are not
> To be honest I was also hoping some feedback from potential users
> interesting in testing those patches. And maybe there are some well
> known (and free) benches that I could challenge ?
I don't know of any, sorry :-(
It would be very useful to have a good set of std::lib benchmarking tests.
https://github.com/hiraditya/std-benchmark does have a umap.cpp test
but it's *very* basic (like most of the tests there - that project
only seems to have good benchmarks for strings).
prev parent reply other threads:[~2022-06-27 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 16:57 François Dumont
2022-06-21 17:12 ` Jonathan Wakely
2022-06-26 20:06 ` François Dumont
2022-06-27 16:18 ` Jonathan Wakely [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).