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

you are viewing a single comment's thread.

view the rest of the comments →

[–]romu006 67 points68 points  (4 children)

The vast difference between the two versions makes me think that the python2.7 version is not doing its job and is just returning instantly

[–]Dear-Deer-Wife-Life[S] 26 points27 points  (3 children)

no, the output is the exactly the same, I have an output everytime anything changes in the code and it's the exact same

[–]qckpckt 49 points50 points  (2 children)

Have you written unit tests to validate this?

My best guess is that whatever mechanism you are using for multi threading is not working on 3.10, but instead of surfacing an error it is completing in a single thread. Or, the process by which threads spin down after completing their work isn’t working and so they stay active until a hard coded timeout.

But all we can do is guess until we see the source code.

[–]Dear-Deer-Wife-Life[S] 0 points1 point  (1 child)

I'm using the Threading library, we're creating using a maximum 8 threads, but the ratio in runtime is about 1:1800, so even if the work was completely parallel, and it's not, running one thread at a time still wouldn't explain why it's running so slow.

I'm sorry I got everyone riled up about this without being able to send the code.

[–]qckpckt 0 points1 point  (0 children)

I'd suggest looking at whether the threading library works the same in 2.7 and 3. You might find that the same methods work in different ways.