>> Oh, BTW, InteractionVecMap works, right? I got some crashes, but I will >> investigate further (it was before removing persistentInteraction and >> the containers had different types). Its great advantage WRT >> parallelization is that it has operator[uint], which is usable by >> openMP. You said once it was even faster than InteractionVecSet, right? >> > > Yes, it works. I get speedup 18% just now > (152 iter/sec with InteractionVecSet and 180 iter/s with InteractionVecMap). > Cool :-) In that case it should be the default, right?
I will commit multi-thread capable BexContainer tonight (should be _very_ low overhead, since there are no locks, but it is safe for concurrent access) and the we can start openMPification of engines and see how well it will scale. V. _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
