On Mon, Jan 14, 2013 at 1:32 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While working on preparation for a Py3k port, I've stumbled across a
fundamental issue with how ZODB structures its API. Do we intend that
client code do the following::
On Mon, Jan 14, 2013 at 7:20 PM, Tres Seaver tsea...@palladion.com wrote:
...
I'm tempted to rename the 'DB.py' module 'db.py', and jam in a BBB entry
in sys.modules for 'ZODB.DB'; likewise, I am tempted to rename the
'FileStorage.py' package 'filestorage', its same-named module
Hello all,
I'm looking to speed up my server and it seems memcached would be a good
way to do it - at least for the `Catalog` (I've already put the catalog in
a separate
zodb with a separate zeoserver with persistent client caching enabled and it
still doesn't run as nice as I like...)
I've
On Tue, Jan 15, 2013 at 3:10 PM, Jim Fulton j...@zope.com wrote:
On Tue, Jan 15, 2013 at 12:00 PM, Claudiu Saftoiu csaft...@gmail.com
wrote:
Hello all,
I'm looking to speed up my server and it seems memcached would be a good
way to do it - at least for the `Catalog` (I've already put
On Tue, Jan 15, 2013 at 2:07 PM, Leonardo Santagada santag...@gmail.comwrote:
On Tue, Jan 15, 2013 at 3:10 PM, Jim Fulton j...@zope.com wrote:
On Tue, Jan 15, 2013 at 12:00 PM, Claudiu Saftoiu csaft...@gmail.com
wrote:
Hello all,
I'm looking to speed up my server and it seems
On Tue, Jan 15, 2013 at 2:08 PM, Claudiu Saftoiu csaft...@gmail.com wrote:
On Tue, Jan 15, 2013 at 2:07 PM, Leonardo Santagada santag...@gmail.com
wrote:
On Tue, Jan 15, 2013 at 3:10 PM, Jim Fulton j...@zope.com wrote:
On Tue, Jan 15, 2013 at 12:00 PM, Claudiu Saftoiu csaft...@gmail.com
On Tue, Jan 15, 2013 at 5:15 PM, Claudiu Saftoiu csaft...@gmail.com wrote:
You can't cause a specific object (or collection of objects) to stay
ion the cache, but if you're working set is small enough to fit in
the memory or client cache, you can get the same effect.
So just setting the
So, first, a concise partial answer to a previous question:
ZODB provides an in-memory object cache. This is non-persistent.
If you restart, it is lost. There is a cache per connection and the
cache size is limited by both object count and total object size (as
estimated by database record
On Tue, Jan 15, 2013 at 2:40 PM, Jim Fulton j...@zope.com wrote:
So, first, a concise partial answer to a previous question:
ZODB provides an in-memory object cache. This is non-persistent.
If you restart, it is lost. There is a cache per connection and the
cache size is limited by both
On Tue, Jan 15, 2013 at 2:45 PM, Claudiu Saftoiu csaft...@gmail.com wrote:
On Tue, Jan 15, 2013 at 2:40 PM, Jim Fulton j...@zope.com wrote:
So, first, a concise partial answer to a previous question:
ZODB provides an in-memory object cache. This is non-persistent.
If you restart, it is
10 matches
Mail list logo
