Sébastien Sablé
added the comment:
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.
__________________________________
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1234>
__________________________________
Index: configure.in
===================================================================
--- configure.in (révision 365)
+++ configure.in (copie de travail)
@@ -1782,6 +1782,8 @@
SunOS/5.8) AC_DEFINE(HAVE_BROKEN_POSIX_SEMAPHORES, 1,
Define if the Posix semaphores do not work on your system)
;;
+ AIX/5) AC_DEFINE(HAVE_BROKEN_POSIX_SEMAPHORES, 1,
+ Define if the Posix semaphores do not work on your system)
esac
AC_MSG_CHECKING(if PTHREAD_SCOPE_SYSTEM is supported)
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
