Re: [ZODB-Dev] Optimizing RelStorage Packing for large DBs

2013-11-18 Thread Jan-Wijbrand Kolman

On 11/16/13 2:01 AM, Jens W. Klein wrote:
 Did I miss something? Any opinions much appreciated!

 Expect updates in this thread :)

We did experience relstorage problems that we think could have been 
related to packing - we're not sure yet. So, I'm following this thread 
and your updates with great interest!


regards, jw

___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] Optimizing RelStorage Packing for large DBs

2013-11-18 Thread Jan-Wijbrand Kolman

On 11/18/13 12:19 PM, Jim Fulton wrote:

On Fri, Nov 15, 2013 at 8:01 PM, Jens W. Klein j...@bluedynamics.com wrote:

I started a new packing script for Relstorage (history free, postgresql). It
is based on incoming reference counting.


Did you look at zc.zodbdgc?  I think it implements something very close to
what you're proposing.  It's been in production for a few years now at ZC.

Not sure if it would need to be updated for relstorage.


AFAICT it does not work against a relstorage backend. Or at least I 
think to understand that from:


http://www.zodb.org/en/latest/documentation/articles/multi-zodb-gc.html

[...This documentation does not apply to RelStorage which has the same 
features built-in, but accessible in different ways. Look at the options 
for the zodbpack script. The –prepack option creates a table containing 
the same information as we are creating in the reference database[...]



regards, jw



___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


[ZODB-Dev] Relstorage: postgres reports IDLE connection after first database write

2013-09-05 Thread Jan-Wijbrand Kolman

Hi,

Recently we realized Relstorage seems to start and never close a 
database connection after the first write. This database connection is 
reported to IDLE in postgres.


Note: this IDLEing connection is only started after adding an object to 
a container - in our testing a Zope application root. Storing an 
attribute on the app root, seems to not result in leaving an IDLEing 
connection.


Quick question: is this expected behaviour?

Kind regards, jw

ps. We suspected that his IDLEing connection keeps postgres from 
succefully running its auto vacuuming task, but we're actually not sure 
about that.


___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev