Hi Nils, Thanks for suggestion for resolving this issue via process-based parallelism, this definitely will do the trick!
On Wed, Nov 2, 2016 at 6:16 AM, Nils Bruin <nbr...@sfu.ca> wrote: > On Tuesday, November 1, 2016 at 1:55:00 PM UTC-4, Fedor Sumkin wrote: >> >> Hi all, >> >> Faced with a quite sad sage bug which arises with interval based >> assumptions and full_simplify()/simplify() in called in parallel. >> >> > Maxima is not threadsafe at all, and the sage design uses a single > (library) sage session, so is not threadsafe (and indeed, things like > global parent structures and global coercion graph structures means that > sage in general is not designed with thread-safety in mind). > > Using a little coarser-grained process-based parallellism should be fine, > and is the approach I think has been used to get parallellism in sage by > most people who've tried. > > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-supp...@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > 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.
