Re: [ZODB-Dev] 8-byte oids
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/13/2009 10:42 PM, Shane Hathaway wrote: Jim Fulton wrote: IPersistent specifies OIDs to be non-empty strings and reserves the 8-byte OID consisting of 8 null characters. Lots of ZODB infrastructure assumes that oids are 8 bytes. I'm tempted to say that oids must be 8-byte strings. +1. The simplified standard promotes interoperability. The difference to the spec before would be that previously strings with less than 8 bytes were allowed? - -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqFBfAACgkQdUt9X/gknwLO9QCeNuLCMk1qElAGJLFGMyagoFZT djMAn3OAPe3BD++9UqzdPMTLwaky0idH =mYEo -END PGP SIGNATURE- ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] 8-byte oids
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/14/2009 08:36 AM, Christian Theune wrote: On 08/13/2009 10:42 PM, Shane Hathaway wrote: Jim Fulton wrote: IPersistent specifies OIDs to be non-empty strings and reserves the 8-byte OID consisting of 8 null characters. Lots of ZODB infrastructure assumes that oids are 8 bytes. I'm tempted to say that oids must be 8-byte strings. +1. The simplified standard promotes interoperability. The difference to the spec before would be that previously strings with less than 8 bytes were allowed? Never mind, reading one of your mails in the other thread actually cleared this up. - -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqFBkgACgkQdUt9X/gknwLJVACgiF5Mk4o++FpLBXft4VGQUYpF oMUAoLoGs1BnnkU6m7ZVhg8xQAmF9Mys =yzsl -END PGP SIGNATURE- ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] RelStorage MySQL - StorageError: Unable to acquire commit lock
On Thu, Aug 13, 2009 at 5:45 PM, Ross J. Reedstromreeds...@rice.edu wrote: On Wed, Aug 12, 2009 at 08:57:39PM -0300, Rudá Porto Filgueiras wrote: On Wed, Aug 12, 2009 at 8:20 PM, Shane Hathawaysh...@hathawaymix.org wrote: A concurrent pack might provide another explanation. Have you ever packed the database? No, there is no pack operation running, only people using Plone to put content. Hmm, it's possible for some things in Plone to keep transactions open a very long time: refreshing the portal_catalog for example. Yes, but there is no portal_catalog update too, only normal catalog operations. I first try to use PostgreSQL, but the time to convert ZODB FileStorage was much larger than MySQL, then I decide to use MySQL. snip I'm interested in knowing why you're moving from ZODB to RelStorage, rather than ZEO? How large is your Data.fs, if you don't mind sharing that information? Our Data.fs is not so large, it's about 5GB but it will almost reach 10GB in six months or before. One important reason to use RelStorage is backend replication possibilities (we are not using it yet) and to give better performance when many people put content in Plone at same time. ZODB is not optmized for large write operations and ZEO will scale poor than RelStraoge in multiple CPU servers, and I know that IO is normaly the problem but we have 15K HBA storage. I really wish some bechmarks scripts to run in our deploy to estimate more acurately how better is RelStorage than ZEO. Shane benchmark results was the main information that compare ZEO and RelStorage and motivate the swicth, and the number of Zope instances that will grow (new server) are another reason. Ross -- Ross Reedstrom, Ph.D. reeds...@rice.edu Systems Engineer Admin, Research Scientist phone: 713-348-6166 The Connexions Project http://cnx.org fax: 713-348-3665 Rice University MS-375, Houston, TX 77005 GPG Key fingerprint = F023 82C8 9B0E 2CC6 0D8E F888 D3AE 810E 88F0 BEDE -- Rudá Porto Filgueiras http://python-blog.blogspot.com ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] Utility to strip version records from storages
I'm working on a utility to strip version records from storages. I plan to release it in a bug fix 3.8 release, probably 3.8.3. It will have some limitations: - It will only convert storages that have an iterator method. I suspect that FileStorages are the only storages that have iterator methods in 3.8 and sooner. (Maybe RelStorages do too.) - It won't give blob records any special treatment. I think it's very unlikely that there will be databases that have both version record and blobs. In any case, it should be possible to copy a blob directory separately after copying the database records. If someone was insane enough to have blobs in versions, then the database records will be stripped but the associated blob files will be left. This is so unlikely that I don't intend to spend time dealing with this possibility. Jim -- Jim Fulton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] ZODB 3.8.3b1
I just released ZODB 3.8.3b1. The most important feature of this release is a new utility, strip_versions, which can be used to strip version data from database file. This is important for databases that contain version data. ZODB 3.9 doesn't support versions and won't open databases containing version data. It would be great if people who have databases with version data would try the utility out. Jim -- Jim Fulton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
