Re: [ZODB-Dev] Ackward PersistentList read Performance

2013-08-13 Thread Joerg Baach
Hi Jim, Malthe, thanks a lot for your advice, really appreciated. I think I get what you mean, but will read up a bit to fully understand whats going on, and to write accordingly (I need the best read throughput I can get, and don't need to bother much with the writes). Cheers, Joerg _

Re: [ZODB-Dev] Ackward PersistentList read Performance

2013-08-13 Thread Jim Fulton
On Tue, Aug 13, 2013 at 9:40 AM, Joerg Baach wrote: > Hi *, > > I was trying to measure the impact of using different kind of objects to > store data in ZODB (disk, ram, time). > > Whats really ackward is the measurement for reading content from > PersistentLists (that are stored in an IOBTree): >

Re: [ZODB-Dev] Ackward PersistentList read Performance

2013-08-13 Thread Malthe Borch
On 13 August 2013 15:40, Joerg Baach wrote: > So, can it really be that using a PersistentList is 300 times slower? Am > I doing something completely wrong, or am I missing something? In your test setup, you commit the transaction and close the connection. This means that when you iterate through

[ZODB-Dev] Ackward PersistentList read Performance

2013-08-13 Thread Joerg Baach
Hi *, I was trying to measure the impact of using different kind of objects to store data in ZODB (disk, ram, time). Whats really ackward is the measurement for reading content from PersistentLists (that are stored in an IOBTree): case a == g.edges=IOBTree() for j in range(1,100): ed