On Thu, 20 Aug 2009, ghtdak wrote: >>> Not surprising. Also, I forgot about the GIL, which truely limits the >>> performance benifits of threading in Python. If anything ever kills >>> Python, I bet it'll be the GIL (but I'm hopeful that it'll get removed >>> before it causes an untimely death...) >> >> Maybe you can remove it :-) >> >> William > > Of course, this is the penultimate reason that going multi-threaded in > python is insane... not only do you get the opportunity to learn all > about synchronization and thread management, you also enjoy non- > deterministic bugs which only take days or weeks to solve whereas more > conventional logic bugs take many many minutes, sometimes even hours. > (From a Keynesian economics perspective, going multi-threaded is > justified just by the added work)
My point was that there is benifit going mutli-threaded: you don't have to manually set up callbacks/fork every time you might block. Whether this simplification is worth the other complexities depends on the program at hand (and probably the programer as well). - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
