hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
Yorlik_ has joined #ste||ar
Yorlik__ has quit [Ping timeout: 250 seconds]
hkaiser has quit [Quit: Bye!]
<pansysk75[m]>
I think I found what my first PR will be, scan_partitioner needs some trivial cleaning up, which is needed before any performance tuning
<pansysk75[m]>
It should be easy to do
<pansysk75[m]>
Also, some algorithms (hpx::remove and hpx::unique) use so little of scan_partitioner's capabilties, that they could be written using some simpler partitioner (plus maybe a small operation afterwards)
<pansysk75[m]>
Might improve performance, will surely improve code readability (because scan_partitioner can get very messy sometimes)
<pansysk75[m]>
* Also, some algorithms (hpx::remove_if and hpx::unique) use so little of scan_partitioner's capabilties, that they could be written using some simpler partitioner
<pansysk75[m]>
Might improve performance, will surely improve code readability (because scan_partitioner can get very messy sometimes)