Message 56228 - Python tracker

➜

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	sable
Recipients	sable
Date	2007-10-04.09:30:54
SpamBayes Score	0.034891266
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
I can confirm that this bug is still present in Python 2.4.1 (and probably later versions) on AIX 5.2 and 5.3. When HAVE_BROKEN_POSIX_SEMAPHORES is not defined at compile time, Python will spend a lot of time in sem_wait, usually when acessing files. The problem does not always happen as it seems to depend on the type of file system in use. In my programm running for 3m30s, Python would call about 400000 time sem_wait and spend about 2mins waiting. When Python is compiled with HAVE_BROKEN_POSIX_SEMAPHORES, the same programm will only take 1m30s. I attach a patch which solves the problem.

I can confirm that this bug is still present in Python 2.4.1 (and
probably later versions) on AIX 5.2 and 5.3.

When HAVE_BROKEN_POSIX_SEMAPHORES is not defined at compile time, Python
will spend a lot of time in sem_wait, usually when acessing files.
The problem does not always happen as it seems to depend on the type of
file system in use.

In my programm running for 3m30s, Python would call about 400000 time
sem_wait and spend about 2mins waiting. When Python is compiled with
HAVE_BROKEN_POSIX_SEMAPHORES, the same programm will only take 1m30s.

I attach a patch which solves the problem.

Files
File name	Uploaded
patch_aix_broken_semaphores.diff	sable, 2007-10-04.09:30:54

History
Date	User	Action	Args
2007-10-04 09:30:55	sable	set	spambayes_score: 0.0348913 -> 0.034891266 recipients: + sable
2007-10-04 09:30:54	sable	set	spambayes_score: 0.0348913 -> 0.0348913 messageid: <[email protected]>
2007-10-04 09:30:54	sable	link	issue1234 messages
2007-10-04 09:30:54	sable	create