On Sun, Dec 9, 2018 at 1:42 PM parisse <bernard.pari...@ujf-grenoble.fr> wrote:
>
> Efficient code does not depend on how you handle it (git, svn or tarballs or 
> whatever).

Efficiency of handling code does depend upon this; fixing a trivial
C++ issue in Giac takes 10 times longer (and takes 10 times more time
and effort from the community around Giac) than in a similar system
hosted, say, on github.


> And I don't think different practices is the real reason why Giac was/is 
> mostly ignored here.

When ODK proposal was being written, we still tried getting Giac to
stop changing distribution tarballs without bumping up version
numbers...


>
> After having done a few tests, I think I know why my code on Q is slower with 
> more threads (if the number of threads exceeds say 2 or 3), it is related to 
> the size of memory the various cores have to acces more than allocation 
> locks, this size is proportionnal to the number of threads if each thread 
> does a different modular computation, and this raises much more cache misses. 
> Which means I must parallelize in each modular computation instead of doing 
> different modulus in parallel.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to