On Mon, Dec 17, 2018 at 10:28 PM serge guelton <
serge.guelton@xxxxxxxxxxxxxxxxxxx> wrote:
On Wed, Dec 12, 2018 at 12:19:28PM +0100, Olivier Borderies wrote:The VM I picked had 16 cores but for unexplained reasons it would not go
tehre
I can reproduce your problems, and after a look at the parallel run,
are *a lot* of shared access in the parallel loop, and you're notetc are
protecting them. All accesses to n_accept, redefinition of new_path
done on shared variable...work on
Thx for the pointer ! Indeed I'm new to omp. I fixed it. Now it does
macOS and Linux. But surprisingly the speedup is much larger in macOS(laptop
and desktop) than on the Linux VM.that from
On macOS the speed up from omp (branch omp) is very much in line with
concurrent.futures (branch master) - as expected since each top loopruns an
entirely separate simulation.results
But on Linux, the speed up is far less. No crash, no warning, good
though. Since it is a VM I cannot really see the CPU use (and check itclimbs
to 100%). I checked that 'apt list --installed | grep omp' shows'libgomp1'....
What kind of reason could explain that ??
Inside a VM... how many core did you allocate to the VM?
If you're ultra-motivated, you could reformat your README to fit into
http://serge-sans-paille.github.io/pythran-stories/
That would be a nice contribution to the project ;-)