connection._reader does the same. So we need to
del them first.
Tell me if I'm right at this. We suffer of unused connections to RDB.
If you have any comments please include my email. Still can't join
zope-dev list.
Thanks anyway.
Igor V. Youdytsky <[EMAIL PROTECTED]>
Russia
--== *
hen where in ZODB source code i can see connection destruction?
Clearing cache and calling _v_database_connection.close() method?
You've just caught me on "thousands" but gave no comments on deletion of
connection instances... but this is the clue
is absurd.
> Again, with 4 threads you should never get more than 4 Filestorage
> connections plus 4 TemporaryStorage connections.
Okay... we moved from Zope 2.7.4, that blocked with small number of
threads and pool_size with high site activity, so we had to increase
those numbers. Anyway
Thanx to everyone who has taken part of this discussion. Tim, Dieter,
Dave. Soory for keeping silence, it gets messy just before New Year
comes.
Back to what i have played with after your advice.
1. I've tried to add gc.collect() in App.ZApplication.Cleanup.__del__(),
so when the connection is re
В Пнд, 02/01/2006 в 15:05 -0500, Tim Peters пишет:
> I'm still baffled by how you get into this state to begin with. Florent
> explained why earlier, and I didn't see a reply to this part:
>
> [Florent Guillaume]
> > Huh are you sure? That would mean you have thousands of threads. Or
> > hundred
If you really want to know the numbers that we have played with...
Zserver threads - pool size
5 - 10
15 - 25
40 - 55
70 - 100
100 - 150
But there is no difference. We raised up these numbers according to the
comming clients, project is involving more and more workers and
different divisions.
In ca
