This repository has been archived by the owner on Dec 22, 2021. It is now read-only.

Make sure HashSet is at least as performant as in the old collections #442

Closed

julienrf opened this issue Feb 9, 2018 · 2 comments

Labels

Milestone

Scala 2.13.0-RC1

Contributor

julienrf commented Feb 9, 2018

In #439 I’ve added benchmarks comparing the main operations of hashsets. In some cases we are still under the performance level of the old HashSet. Also, in some cases ChamHashSet is less performant than HashSet. We have to investigate more before committing to a default Set implementation.

ChamHashSet wins.

The new HashSet wins.

The old HashSet wins!

New HashSet wins (ex æquo with the old one).

ChamHashSet wins for sets with more than 100 elements.

No one wins.

The text was updated successfully, but these errors were encountered:

julienrf added the blocker label

julienrf added this to the 0.11.0 milestone

julienrf added the ready label

julienrf removed this from the 0.11.0 milestone

szeiger added this to the Scala 2.13.0-M5 milestone

Member

SethTisue commented Jun 27, 2018

one specific performance minus is being investigated at scala/scala-dev#525

SethTisue modified the milestones: Scala 2.13.0-M5, Scala 2.13.0-RC1

Member

SethTisue commented Nov 16, 2018

I think is considered resolved now? reopen if you disagree /cc @szeiger @retronym

SethTisue closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.