Skip to content

Conversation

@gfs
Copy link
Contributor

@gfs gfs commented Apr 29, 2020

Fixes slow collection performance regression introduced with gathering results in Memory.

@gfs gfs merged commit a4ab69b into master Apr 29, 2020
@gfs gfs deleted the gfs/#413 branch April 29, 2020 21:25
gfs added a commit that referenced this pull request Apr 29, 2020
* Fix #413.

Collection was being slowed down by the ConcurrentQueue which according to https://stackoverflow.com/questions/19326197/net-4-0-concurrent-collection-performance is actually slower than a standard list.  Tested here and the list was significantly faster (20% cpu usage to 900-1000% on my macbook pro)

* AsParallel.ForAll is faster than Parallel.ForEach

* Add unique constrint on runid and identity.
gfs added a commit that referenced this pull request Apr 29, 2020
* Fix #413.

Collection was being slowed down by the ConcurrentQueue which according to https://stackoverflow.com/questions/19326197/net-4-0-concurrent-collection-performance is actually slower than a standard list.  Tested here and the list was significantly faster (20% cpu usage to 900-1000% on my macbook pro)

* AsParallel.ForAll is faster than Parallel.ForEach

* Add unique constrint on runid and identity.
gfs added a commit that referenced this pull request May 7, 2020
* Fix #413.

Collection was being slowed down by the ConcurrentQueue which according to https://stackoverflow.com/questions/19326197/net-4-0-concurrent-collection-performance is actually slower than a standard list.  Tested here and the list was significantly faster (20% cpu usage to 900-1000% on my macbook pro)

* AsParallel.ForAll is faster than Parallel.ForEach

* Add unique constrint on runid and identity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants