[Leonardo Rochael Almeida]
>> Please add this issue to the Collector, including the test
>> (prefereably without the twisted bits)
[Syver Enstad]
> Eh, what is the Collector?
The zope.org Collectors are here:
http://www.zope.org/Collectors/
and you want the Zope Collector:
http://zope.
Leonardo Rochael Almeida <[EMAIL PROTECTED]> writes:
> Hi Syver,
>
> Please add this issue to the Collector, including the test (prefereably
> without the twisted bits)
>
Eh, what is the Collector?
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://
Hi Syver,
Please add this issue to the Collector, including the test (prefereably
without the twisted bits)
On Thu, 2004-04-22 at 12:57, Syver Enstad wrote:
> [...]
>
> I have a strange case here with ReadConflictErrors. I don't know if
> this is covered already but anyway. I am using ZODB 3.2 s
Toby Dickenson <[EMAIL PROTECTED]> writes:
> On Thursday 22 April 2004 11:43, Syver Enstad wrote:
>
> > cache_deactivate_after sounds interesting. Since I am running ZODB in
> > a web server I don't want the data to timeout and disappear from
> > memory since every object I have should be loaded
On Thursday 22 April 2004 11:43, Syver Enstad wrote:
> cache_deactivate_after sounds interesting. Since I am running ZODB in
> a web server I don't want the data to timeout and disappear from
> memory since every object I have should be loaded at all times.
Thats why ZODB ignores that parameter n
Toby Dickenson <[EMAIL PROTECTED]> writes:
> On Thursday 22 April 2004 10:42, Syver Enstad wrote:
> > I've used the cache_size paramter to the constructor of the DB to good
> > effect. Are there any further gotchas for ensuring that the ZODB stays
> > in memory as much as possible?
>
> Memory usa
On Thursday 22 April 2004 10:42, Syver Enstad wrote:
> I've used the cache_size paramter to the constructor of the DB to good
> effect. Are there any further gotchas for ensuring that the ZODB stays
> in memory as much as possible?
Memory usage scales proportional to the number of threads. Reduci
I've used the cache_size paramter to the constructor of the DB to good
effect. Are there any further gotchas for ensuring that the ZODB stays
in memory as much as possible?
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listin
