From: dgoulet@efficios.com (David Goulet)
Subject: [lttng-dev] [PATCH lttng-tools] Fix: hash table growth (for small tables) should be limited (v2)
Date: Thu, 29 Aug 2013 12:54:51 -0400 [thread overview]
Message-ID: <521F7CDB.7050504@efficios.com> (raw)
In-Reply-To: <20130827221104.GA13930@Krystal>
Merged!
Mathieu Desnoyers:
> Buckets with many entries encountered in a hash table could cause it to
> grow to a large size, beyond the scope for which this mechanism is
> expected to play a role when node accounting is available. Indeed, when
> the hash table grows to larger size, split-counter node accounting is
> expected to deal with resize/shrink rather than relying on an heuristic
> based on the largest bucket size.
>
> This is fixing an issue where we see hash tables sometimes reaching 65k
> entries index (65536*8 = 524288 bytes) for a workload limited to adding
> 1000 entries and then removing all of them, done in a loop (random
> keys).
>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> ---
> diff --git a/src/common/hashtable/rculfhash.c b/src/common/hashtable/rculfhash.c
> index b430a3d..ebdc4ff 100644
> --- a/src/common/hashtable/rculfhash.c
> +++ b/src/common/hashtable/rculfhash.c
> @@ -726,9 +726,32 @@ void check_resize(struct cds_lfht *ht, unsigned long size, uint32_t chain_len)
> if (chain_len > 100)
> dbg_printf("WARNING: large chain length: %u.\n",
> chain_len);
> - if (chain_len >= CHAIN_LEN_RESIZE_THRESHOLD)
> - cds_lfht_resize_lazy_grow(ht, size,
> - cds_lfht_get_count_order_u32(chain_len - (CHAIN_LEN_TARGET - 1)));
> + if (chain_len >= CHAIN_LEN_RESIZE_THRESHOLD) {
> + int growth;
> +
> + /*
> + * Ideal growth calculated based on chain length.
> + */
> + growth = cds_lfht_get_count_order_u32(chain_len
> + - (CHAIN_LEN_TARGET - 1));
> + if ((ht->flags & CDS_LFHT_ACCOUNTING)
> + && (size << growth) >= (1UL << COUNT_COMMIT_ORDER)) {
> + /*
> + * If ideal growth expands the hash table size
> + * beyond the "small hash table" sizes, use the
> + * maximum small hash table size to attempt
> + * expanding the hash table. This only applies
> + * when node accounting is available, otherwise
> + * the chain length is used to expand the hash
> + * table in every case.
> + */
> + growth = COUNT_COMMIT_ORDER -
> + cds_lfht_get_count_order_u32(size);
> + if (growth <= 0)
> + return;
> + }
> + cds_lfht_resize_lazy_grow(ht, size, growth);
> + }
> }
>
> static
>
prev parent reply other threads:[~2013-08-29 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 22:01 [lttng-dev] [PATCH lttng-tools] Fix: hash table growth (for small tables) should be limited Mathieu Desnoyers
2013-08-27 22:11 ` [lttng-dev] [PATCH lttng-tools] Fix: hash table growth (for small tables) should be limited (v2) Mathieu Desnoyers
2013-08-29 16:54 ` David Goulet [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521F7CDB.7050504@efficios.com \
--to=dgoulet@efficios.com \
/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