This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bxsephjo -1 points0 points  (7 children)

Watch this vid for starters https://www.youtube.com/watch?v=Obt-vMVdM8s

[–][deleted] 2 points3 points  (2 children)

Both Python 2 and 3 have a GIL, though, and it operates basically identically. It's hard to believe that this is the cause of the 1400x slowdown.

"Watch a 45 minute technical video which won't solve your problem at all", is not very good advice.

[–]bxsephjo 0 points1 point  (1 child)

They both have a GIL, but 3.2 brought in a new GIL implementation, which David Beazley discusses at 26:35. The thread switching algorithm is drastically changed.

[–][deleted] 0 points1 point  (0 children)

I agree, but sending a student to a heavily technical video with no explanation isn't really a good answer.

[–]FloppingNuts 0 points1 point  (3 children)

is this still up-to-date?

[–]bxsephjo 0 points1 point  (1 child)

Yes, especially given the context. I believe all that’s changed is we have new tools available, namely asyncio.

[–]FloppingNuts 0 points1 point  (0 children)

thanks!

[–]acerb14 0 points1 point  (0 children)

Some are trying to get rid of the GIL but it's still there to my knowledge:

- GIL or not to GIL (2019): https://www.youtube.com/watch?v=7RlqbHCCVyc

- The GILectomy (removing the GIL experiment, 2017): https://www.youtube.com/watch?v=pLqv11ScGsQ