This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Hashtable
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Arkady <arkady dot miasnikov at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Mon, 10 Jul 2017 11:20:46 -0400
- Subject: Re: Hashtable
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fche at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com DAFAA8048C
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com DAFAA8048C
- References: <CANA-60ovD=B6BC-d4cCB6P+LEtwq=CYS7YU+4LG-MV1676Du9g@mail.gmail.com>
arkady.miasnikov wrote:
> [...]
> From the tests it appears that associative maps contribute significant
> part of the overhead. I was thinking about replacing the maps with a
> simple hashtable like this one (this is not production code)
> https://gist.github.com/larytet/c306d470f7b032c796efad15dcd609a9
The systemtap maps are already hash tables. The complication here is
that you're using them in a highly contended way, so locking effects
dominate algorithmic ones. PR10796 is probably more relevant to your
case.
- FChE