On Mon, Sep 14, 2009 at 3:52 PM, Shane Hathaway wrote:
> Benji York wrote:
>>
>> On Mon, Sep 14, 2009 at 2:44 PM, Shane Hathaway
>> wrote:
>>>
>>> People have been looking at these performance charts for quite a while:
>>
>> Are the benchmarks publicly available? I looked through the blog posts
Benji York wrote:
> On Mon, Sep 14, 2009 at 2:44 PM, Shane Hathaway wrote:
>> People have been looking at these performance charts for quite a while:
>
> Are the benchmarks publicly available? I looked through the blog posts
> and svn.zope.org but couldn't find them.
http://svn.zope.org/relstor
On Mon, Sep 14, 2009 at 2:44 PM, Shane Hathaway wrote:
> People have been looking at these performance charts for quite a while:
Are the benchmarks publicly available? I looked through the blog posts
and svn.zope.org but couldn't find them.
--
Benji York
Senior Software Engineer
Zope Corporatio
Chris Withers wrote:
> Shane Hathaway wrote:
>> Chris Withers wrote:
>>> I thought RelStorage was slow at packing?
>> Not anymore. I optimized packing last December/January and it has been
>> plenty fast ever since, AFAIK.
>
> Interesting. Got any metrics on its speed compared to FileStorage,
>
Shane Hathaway wrote:
> Chris Withers wrote:
>> I thought RelStorage was slow at packing?
>
> Not anymore. I optimized packing last December/January and it has been
> plenty fast ever since, AFAIK.
Interesting. Got any metrics on its speed compared to FileStorage,
including packing?
cheers,
Chris Withers wrote:
> I thought RelStorage was slow at packing?
Not anymore. I optimized packing last December/January and it has been
plenty fast ever since, AFAIK.
Shane
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/W
Shane Hathaway wrote:
>> There is a .old file there, but it was last modified over a week ago.
>
> The analysis phase of packing can take a long time. A week is too much,
> though. :-)
Yeah, this is off the back of an automated pack/backup/unpack/verify to
keep two storages in sync on two data
Chris Withers wrote:
> I've got a ZODB that's ballooned and I'm now having problems packing
> with zeopack.
>
> I tried with zeopack, which appeared to just hang (still in top, but no
> cpu usage for an hour or two), so I ctrl-c'ed it.
>
> Now when I try, I just get the text "Already packing" b
On Mon, Sep 14, 2009 at 10:43 AM, David Glick wrote:
> On Sep 14, 2009, at 7:04 AM, Jim Fulton wrote:
>>
>> On Mon, Sep 14, 2009 at 7:10 AM, Chris Withers
>> wrote:
>>>
>>> Jim Fulton wrote:
ZODB doesn't provide any direct support because it has no notion of
tree.
>>>
>>> Does it h
On Sep 14, 2009, at 7:04 AM, Jim Fulton wrote:
> On Mon, Sep 14, 2009 at 7:10 AM, Chris Withers
> wrote:
>> Jim Fulton wrote:
>>>
>>> ZODB doesn't provide any direct support because it has no notion
>>> of tree.
>>
>> Does it have any notion of object size on disk for a given object?
>
> Not d
Hi All,
I've got a ZODB that's ballooned and I'm now having problems packing
with zeopack.
I tried with zeopack, which appeared to just hang (still in top, but no
cpu usage for an hour or two), so I ctrl-c'ed it.
Now when I try, I just get the text "Already packing" back.
There is a .old file
On Mon, Sep 14, 2009 at 7:10 AM, Chris Withers wrote:
> Jim Fulton wrote:
>>
>> ZODB doesn't provide any direct support because it has no notion of tree.
>
> Does it have any notion of object size on disk for a given object?
Not directly, but you can do:
len(ob._p_jar.db().storage.load(ob._p_o
On Sep 14, 2009, at 13:27 , Chris Withers wrote:
Jens Vagelpohl wrote:
Sadly, when you're trying to figure out which folder is using all
the
space on a disk that's running out of space, that's not practical...
How about simply writing a script that crawls the ZODB and gives
you paths and s
On 14.09.09 13:27, Chris Withers wrote:
> Jens Vagelpohl wrote:
>
>>
>>> Sadly, when you're trying to figure out which folder is using all the
>>> space on a disk that's running out of space, that's not practical...
>>>
>> How about simply writing a script that crawls the ZODB and gi
Jens Vagelpohl wrote:
>
>> Sadly, when you're trying to figure out which folder is using all the
>> space on a disk that's running out of space, that's not practical...
>
> How about simply writing a script that crawls the ZODB and gives you
> paths and sizes?
Indeed, and what's the magic incan
On Sep 14, 2009, at 13:10 , Chris Withers wrote:
Jim Fulton wrote:
ZODB doesn't provide any direct support because it has no notion of
tree.
Does it have any notion of object size on disk for a given object?
In Zope 2, you could export the folder and look at the size of the
export.
Sad
Jim Fulton wrote:
> ZODB doesn't provide any direct support because it has no notion of tree.
Does it have any notion of object size on disk for a given object?
> In Zope 2, you could export the folder and look at the size of the export.
Sadly, when you're trying to figure out which folder is us
On Mon, Sep 14, 2009 at 5:55 AM, Chris Withers wrote:
> Hi All,
>
> As the subject line says with the following definitions:
>
> - size = size on disk, in Mb
>
> - subtee = Zope folderish type things, in this case...
ZODB doesn't provide any direct support because it has no notion of tree.
In Zo
Adam GROSZER wrote:
> Hello,
>
> +1 on that. Sometimes copy operations (over the network) screw up some
> bits. Happens rarely but then it hits hard.
>
> Monday, September 14, 2009, 10:13:39 AM, you wrote:
>
> CT> Hmm. Haven't seen that. My guess would be some low-level data corruption.
>
> CT>
Hi All,
As the subject line says with the following definitions:
- size = size on disk, in Mb
- subtee = Zope folderish type things, in this case...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
__
Hello,
+1 on that. Sometimes copy operations (over the network) screw up some
bits. Happens rarely but then it hits hard.
Monday, September 14, 2009, 10:13:39 AM, you wrote:
CT> Hmm. Haven't seen that. My guess would be some low-level data corruption.
CT> Christian
--
Best regards,
Adam GR
I've sent a mail to this list on 05/26/09 reporting a similar issue.
Regards,
Pedro
Christian Theune wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/14/2009 10:06 AM, Chris Withers wrote:
>
>> Hi All,
>>
>> Anyone ever see this?
>>
>> Traceback (most recent call last):
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2009 10:06 AM, Chris Withers wrote:
> Hi All,
>
> Anyone ever see this?
>
> Traceback (most recent call last):
>File "/opt/Zope-2.9//bin/repozo.py", line 517, in ?
> main()
>File "/opt/Zope-2.9//bin/repozo.py", line 510, in main
Hi All,
Anyone ever see this?
Traceback (most recent call last):
File "/opt/Zope-2.9//bin/repozo.py", line 517, in ?
main()
File "/opt/Zope-2.9//bin/repozo.py", line 510, in main
do_backup(options)
File "/opt/Zope-2.9//bin/repozo.py", line 450, in do_backup
reposz, reposum
24 matches
Mail list logo
