Failed requests:9993 But I did have 1564.21 requests per second
doh :-)
anyway http://87.98.218.86/gil.py seem to work ?
http://87.98.218.86/bench.txt (added my apache.conf)
http://87.98.218.86/bench.htm
So did we find a gil bug in Grahams mighty code ?
On Oct 6, 10:18 am, Graham Dumpleton [EMAIL PROTECTED]
wrote:
2008/10/6 gert [EMAIL PROTECTED]:
Failed requests: 9993 But I did have 1564.21 requests per second
doh :-)
anywayhttp://87.98.218.86/gil.pyseem to work ?
http://87.98.218.86/bench.txt(added my apache.conf)
BTW, one of the possible causes of your problem could be the use of a
third party C extension module that doesn't work properly for multiple
sub interpreters. Yes, I know that Trac may be running with
WSGIApplicationGroup of %{GLOBAL}, but if that same C extension module
is being used in Django
On Oct 6, 10:33 am, gert [EMAIL PROTECTED] wrote:
On Oct 6, 10:18 am, Graham Dumpleton [EMAIL PROTECTED]
wrote:
2008/10/6 gert [EMAIL PROTECTED]:
Failed requests: 9993 But I did have 1564.21 requests per second
doh :-)
anywayhttp://87.98.218.86/gil.pyseemto work ?
On 06-10-2008, gert wrote:
On Oct 6, 10:33 am, gert [EMAIL PROTECTED] wrote:
On Oct 6, 10:18 am, Graham Dumpleton [EMAIL PROTECTED]
wrote:
2008/10/6 gert [EMAIL PROTECTED]:
Failed requests: 9993 But I did have 1564.21 requests per second
doh :-)
Hi,
[Mon Oct 06 15:08:52 2008] [notice] Apache/2.2.4 (Linux/SUSE)
mod_ssl/2.2.4 OpenSSL/0.9.8e mod_wsgi/2.3 Python/2.5.1 configured --
resuming normal operations
[Mon Oct 06 15:09:01 2008] [crit] [Mon Oct 06 15:09:01 2008] file
http_filters.c, line 346, assertion readbytes 0 failed
[Mon Oct
On 06-10-2008, William Dode wrote:
...
The only problem is that there is not a lot of db pool utilities and
dbutils is one of the most famous...
I reported the problem on the dbutils list
--
William Dodé - http://flibuste.net
Informaticien Indépendant
On 04-10-2008, Graham Dumpleton wrote:
BTW, if I am right, you would see the behaviour you expect to see if you use:
WSGIApplicationGroup %{GLOBAL}
More or less, it give me alternatively two differents local instances...
But i'm agree with your analyze, that to use threading.local is not
2.0.8 definitely fixed some segfaults on my end.
So far, since September 30 I have not seen any segmentation faults.
Seems that upgrade to 2.0.8 and using %{GLOBAL} solved the problem.
Graham, thank you for the support! :)
--
Maciej Wisniowski
Will this share connections between requests ?
import _mysql
db = _mysql.connect('127.0.0.1','root','root','www')
def application(environ, start_response):
db.query(SELECT test FROM test)
row = db.store_result()
v = row.fetch_row()[0][0]
db.close()
response_headers =
On Oct 6, 11:48 pm, gert [EMAIL PROTECTED] wrote:
Will this share connections between requests ?
import _mysql
db = _mysql.connect('127.0.0.1','root','root','www')
def application(environ, start_response):
db.query(SELECT test FROM test)
row = db.store_result()
v =
2008/10/6 gert [EMAIL PROTECTED]:
On Oct 6, 10:33 am, gert [EMAIL PROTECTED] wrote:
On Oct 6, 10:18 am, Graham Dumpleton [EMAIL PROTECTED]
wrote:
2008/10/6 gert [EMAIL PROTECTED]:
Failed requests:9993 But I did have 1564.21 requests per second
doh :-)
Thank you, thank you, thank you! I'll give this a try tonight and see
how long before someone tells me Trac is down. :-)
On Mon, Oct 6, 2008 at 9:08 PM, Graham Dumpleton
[EMAIL PROTECTED] wrote:
2008/10/7 Todd O'Bryan [EMAIL PROTECTED]:
I think you may have hit the nail on the head. The
13 matches
Mail list logo
