All of lore.kernel.org
 help / color / mirror / Atom feed
From: 陈志文 <zwchen@aimlab.org>
To: lttng-dev@lists.lttng.org
Subject: A strange problem encountered using urcu-based hash table
Date: Fri, 18 Dec 2015 18:02:20 +0800	[thread overview]
Message-ID: <CAN0x0o0AEp=jMF1HD1sunGegTc9D-76x5hGVMf+8CLvoxmNiaw__22970.3203346164$1450465079$gmane$org@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 814 bytes --]

Hi, I'm a Ph.D from Hunan University of China. Recently, our group are
tending to analysis concurrent hash tables using different synchronization
mechanisms, urcu-based hashing is one of our targets. Today, we running an
urcu-based hash table with only ten percent update operations. We found its
CPU utilization is only 3% (while in a read-only workload, the CPU
utilization is 50%). Is there any writer performance limits for urcu? Or
why this happened in your eye?

There is our platform information: Intel SandyBridge EP with 2 sockets,
each sockets with 8 cores and 2 physical threads for each core. OS: Ubuntu
14.04 LTS.
Experimental configuration: 16 threads, ten percent of update operations
and 1 million initial elements in hash table.

We are looking forward for your reply.

Thanks!

-- 
aimlab zwchen

[-- Attachment #1.2: Type: text/html, Size: 1014 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2015-12-18 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 10:02 陈志文 [this message]
     [not found] <CAN0x0o0AEp=jMF1HD1sunGegTc9D-76x5hGVMf+8CLvoxmNiaw@mail.gmail.com>
2015-12-18 20:26 ` A strange problem encountered using urcu-based hash table Mathieu Desnoyers

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='CAN0x0o0AEp=jMF1HD1sunGegTc9D-76x5hGVMf+8CLvoxmNiaw__22970.3203346164$1450465079$gmane$org@mail.gmail.com' \
    --to=zwchen@aimlab.org \
    --cc=lttng-dev@lists.lttng.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.