* not be reading this list
actively.
--
Martijn Pieters
___
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
garbage
collection.
--
Martijn Pieters
___
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
act as a BlobStorage, NEO can not.
Anything else different? Did you make any performance comparisons
between RelStorage and NEO?
--
Martijn Pieters
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
switch;
this makes sure your environment does not try to import
globally-installed packages.
--
Martijn Pieters
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo
On Thu, Jun 14, 2012 at 5:14 PM, Paul Winkler sli...@gmail.com wrote:
That's backwards, I'm sure you just made a typo but I don't want Ralf
to get confused :)
Yeah, my mistake. *with*, not *without*. Sorry!
--
Martijn Pieters
___
For more
of persistent objects if parts need changing over
time. Future commits would be a lot smaller that way. I'd parse out
the original large dictionary in a separate process, perhaps chunk the
commits (so build up the structure over several commits).
--
Martijn Pieters
on SIGUSR1, like the Zope
signalstack product does (see
http://svn.plone.org/svn/collective/Products.signalstack/trunk/Products/signalstack/__init__.py
for the exact code to bind the signal handler). That'll tell you
exactly what each thread is busy with when you send the signal.
--
Martijn
locked up,
then it could be that the server is not answering your is_alive
request at all because it is waiting for a thread to free up first.
--
Martijn Pieters
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev
all ZODB blobs also live in the
same database. Performance is quite decent but the customer doesn't
try to store more than a few MBs per file.
Better keep them in a NFS setup for most cases.
--
Martijn Pieters
___
For more information about ZODB, see
ZEO server and attempt to pack again. Now it should log
the exception instead of None.
--
Martijn Pieters
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb
for people on this list to analyze.
I cannot promise anyone will, of course, but if someone could and the
pickle is shown to only contain primitive data types (no references at
all) then the pass is certainly going to solve your problem.
--
Martijn Pieters
there.
--
Martijn Pieters
___
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
at where to start debugging this. Any hints from anyone?
--
Martijn Pieters
___
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
has weird
edge cases.)
The test rig is not using RAC. In fact, the production environment no
longer uses RAC either.
--
Martijn Pieters
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https
of the stock FileStorage implementation, not on public ZODB
APIs. I haven't touched the archetypes History code in 5 years at
least though, so I am not sure about this.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http
particular problem though.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
On Tue, Jun 14, 2011 at 22:22, Martijn Pieters m...@zopatista.com wrote:
I am considering altering the ON COMMIT behaviour of the
temp_blob_chunk table to TRUNCATE to extend this behaviour to all
remaining blob rows on commit. However, such events should be rare
enough
On Wed, Jun 15, 2011 at 16:23, Martijn Pieters m...@zopatista.com wrote:
Last but not least I'll need to write a migration script for those
users of RelStorage 1.5.0b2 already in production.
I have figured out how to do this (see
http://archives.postgresql.org/pgsql-general/2009-01/msg00771
without issue.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
in that it let's you specify files directly to upload from or
download to.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo
after my refactor. Any reason to keep it, other than that
others whom already are using 1.5b2 on an Oracle database will now
have to drop that column again (or set it to a default value of 0 on
insert)? Should the code support reading blob chunks still?
--
Martijn Pieters
On Thu, Jun 9, 2011 at 22:03, Martijn Pieters m...@zopatista.com wrote:
I'm retaining the schema; there is a chance people have updated to
1.5b2 already and are using blobs in production. My refactor maintains
compatibility with the chunked blob storage.
I've attached my patch for review
package bit me at some
point, disabling our cluster. Luckily a swift restart of one of the
clients reinstated the 1.4 version quickly. :-) We are not quite ready
for a full 1.5.0 upgrade just yet.. ;-)
--
Martijn Pieters
___
For more information about
, but not 5.5 yet.
The nowait locking strategy worked beautifully on our mammoth pack, so
I've committed it to RelStorage trunk. I didn't get a chance to test
it against MySQL 5.1 though, but the MySQL changes were minimal and
mirrored those for the Oracle version.
--
Martijn Pieters
deletion SQL statements have been optimized for
MySQL, but not for the history-free version. Wouldn't those statements
not also benefit from using a JOIN?
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis
BlobCacheChecker.loaded with check=True (the default). Try calling it
with check=False instead.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org
established that the cache cleanup in
RelStorage is to blame here, so we can focus on
_check_blob_cache_size, specifically on line 490 and further.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB
to RelStorage SVN after we
tried it on for size, in the next few days.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman
On Fri, Feb 25, 2011 at 12:48, Shane Hathaway sh...@hathawaymix.org wrote:
Do your best and I'll take a look after you've committed the patches to
the trunk. :-)
The pack progress and two-phase pack patches have been committed.
--
Martijn Pieters
On Thu, Feb 24, 2011 at 16:56, Martijn Pieters m...@zopatista.com wrote:
I see a lot of transaction aborted errors on the ZODB multi-thread
tests with this patch in place, so I'll have to investigate more.
Thread debugging joy!
In the end it was a simple mistake in the PostgreSQL version
On Wed, Feb 23, 2011 at 15:08, Martijn Pieters m...@zopatista.com wrote:
I've started a optimistic locking strategy patch in my patch queue,
contains this locking strategy change only for now:
https://bitbucket.org/mjpieters/relstorage-mq/src/tip/optimistic_commitlock_pack.patch
I've made
On Wed, Feb 23, 2011 at 14:41, Martijn Pieters m...@zopatista.com wrote:
I've moved this patch to bitbucket at
https://bitbucket.org/mjpieters/relstorage-mq/src/tip/twophasepack.patch
and updated the README a little more to document the options to
zodbpack.
The two-phase pack patch has been
On Thu, Feb 24, 2011 at 14:26, Martijn Pieters m...@zopatista.com wrote:
I've made progress on the patch this afternoon. Next up are tests for
both patches. The above patch now uses the nowait locking strategy to
run pack batches. It has been renamed though, and now lives at:
https
, presumably
queries during a GC run should be easier on the database as there is
less data to scan through.
--
Martijn Pieters
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev
On Tue, Feb 22, 2011 at 21:41, Martijn Pieters m...@zopatista.com wrote:
BTW, should I just commit the patch, or do you want to integrate it
yourself?
Updated patch attached; added the options changes to component.xml and
README.txt.
--
Martijn Pieters
twophasepack.patch
Description: Binary
On Wed, Feb 23, 2011 at 11:55, Martijn Pieters m...@zopatista.com wrote:
Updated patch attached; added the options changes to component.xml and
README.txt.
I've moved this patch to bitbucket at
https://bitbucket.org/mjpieters/relstorage-mq/src/tip/twophasepack.patch
and updated the README
On Tue, Feb 22, 2011 at 21:41, Martijn Pieters m...@zopatista.com wrote:
I'll look into working the locking idea into a patch too,
but I'll need help with supporting Postgres and MySQL as I don't know
their locking semantics.
Both MySQL and Oracle support lock timeouts and already use
-intrusive background operation. Is this a viable scenario?
--
Martijn Pieters
twophasepack.patch
Description: Binary data
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
a mirrorred test cluster high on our
wishlist, but having the database packed first would make that easier
given the size of the database now. In the future however, copying
back the prepared pack tables is an excellent prospect.
--
Martijn Pieters
39 matches
Mail list logo
