This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author james.mccormack
Recipients gpolo, james.mccormack, josh.r, paul.moore, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2019-03-25.19:53:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553543638.17.0.661514721788.issue36408@roundup.psfhosted.org>
In-reply-to
Content
I can run four independent processes (i.e. not using multiprocessing, with no links at all between them) yet the results show that only one core is running. Where is this lock taking place? Why would a tkinter process need to know about another tkinter process?
	
A little bit of history I have learned is that prior to Windows 7, the GDI sub-system imposed a global lock system-wide so that only one process (one thread) could write to the display at one time. This meant in effect it was a one-core GUI desktop. From Windows 7, this was supposed to have been 'fixed', but all I have read is that the "GDI lock became more fine-grained, reducing concurrency bottlenecks". I wonder did anyone ever measure performance in real-world scenarios to demonstrate whether there was in fact any improvement?
History
Date User Action Args
2019-03-25 19:53:58james.mccormacksetrecipients: + james.mccormack, paul.moore, tim.golden, gpolo, zach.ware, serhiy.storchaka, steve.dower, josh.r
2019-03-25 19:53:58james.mccormacksetmessageid: <1553543638.17.0.661514721788.issue36408@roundup.psfhosted.org>
2019-03-25 19:53:58james.mccormacklinkissue36408 messages
2019-03-25 19:53:58james.mccormackcreate