Re: GIL, threads and scheduling - performance cost

[EMAIL PROTECTED] a écrit : > Merci Pierre, > > Yes I agree and plan to move more to C/C++ and releasing the GIL when > entering C/C++. > > I also need to understand my original question re GIL and rescheduling. > I fear that lock/unlock too often is also causing delays due to context > switching

Re: GIL, threads and scheduling - performance cost

Merci Pierre, Yes I agree and plan to move more to C/C++ and releasing the GIL when entering C/C++. I also need to understand my original question re GIL and rescheduling. I fear that lock/unlock too often is also causing delays due to context switching. BTW do you have any hints/comments on SWI

Re: GIL, threads and scheduling - performance cost

[EMAIL PROTECTED] a écrit : > Hi all, > > Wondering if a GIL lock/unlock causes a re-schedule/contect swap when > embedding Python in a multi-threaded C/C++ app on Unix ? > > If so, do I have any control or influence on this re-scheduling ? > > The app suffers from serious performance degradatio

GIL, threads and scheduling - performance cost

Hi all, Wondering if a GIL lock/unlock causes a re-schedule/contect swap when embedding Python in a multi-threaded C/C++ app on Unix ? If so, do I have any control or influence on this re-scheduling ? The app suffers from serious performance degradation (compared to pure c/C++) and high context