Hi Marcel. Yeah, each iteration it adds a node, saves the session, checks-in the node, and then moves on to the next (random data, several properties). If I bump up the memory, it certainly works a lot better (-Xmx300M). Its really quite basic.
The error is simple an OutMemoryException that happens between 400 and 700 nodes. I will try the other persistence manager test, probably a good idea to see if it is related to the implementation PM for Derby (probably not). I will post back the results.
From what people are saying, it doesn't sound like I am trying to do
anything too wierd, and that there have been some tests done in the past (any one that can point me to them it would be appreciated). On 9/1/06, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
Michael Neale wrote: > It screams through for about the first 100 nodes, but then slows down in > that familiar exponential way, generally failing around 500 nodes. If I > start it up again, and continue adding more, it powers on just fine. can you please clarify what exactly your code does? I understand there is node somewhere in the workspace where you start to add child nodes. each child nodes has a couple of properties you mentioned. Do you save the session whenever you add 1 child node? or after a certain number of child nodes? What exception is thrown when you reach the 500 child nodes? regards marcel
