Performance/Scalability

Hi,

 

I've been playing around with Ozone and the Garage/Car tutorial.

 

This is my first experience with ODB's but the concepts and theory are very
intriguing!

Nice work!

 

 

I have a real world case where the data structure of the Garage/Car tutorial
fits nicely with.

That is a single collection (Garage) stored by name that includes many
objects.  In my

case I will not have a known key to associate with my "Car" objects.
Instead my objects

will appear from clients using my webapp and will have a small number of
fields that can 

only have a few different values and only be really unique by the timestamp
that they are received by.

But of course I won't know these timestamps so I wouldn't be able to
retrieve off this "key" later.

 

Also, I want to store millions of these objects.

 

If I modify the tutorial to have a big loop adding cars called "1", "2",
"3", etc. then the loop 

runs very slowly.  I'm guessing because with every object that is added, the
entire data

structure has to be rewritten?  On my machine (700mhz, 512 mb, SuSE 8.1, JVM
1.4.2)

I was writing 1000 records every 20 minutes.  This is very much slower than
I require.

 

Also, I ran out of memory as I approached 20000 records.  I assume this is
because the entire

data structure was in RAM.

 

I am positive that I am not using this in the proper way to accomplish this
objective of fast

write/read operations as well as running within a reasonable memory
constraint.  Do you have

suggestions on how to code something like this?

 

Thank you for your suggestions!

 

David.