Closed GoogleCodeExporter closed 9 years ago
Interesting. dense_hash_set does a lot of comparisons against the empty-key,
so if
those comparisons are slow, dense_hash_set will also be slow. Since your set
uses a
pointer for the key, it would be great if you could do set_empty_key(NULL), and
then
have your comparison function do something really fast when one of the args is
NULL.
That should get performance back.
I'm closing this as a bug report. If you'd like to discuss further, feel free
to
mail to google-sparsehash@googlegroups.com
Original comment by csilv...@gmail.com
on 27 Feb 2009 at 10:33
Original issue reported on code.google.com by
ory...@gmail.com
on 27 Feb 2009 at 10:08