[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Architecture/design questions

On Tuesday, March 6, 2001, at 09:19 PM, P C wrote:

> 1. Does Ozone use Java serialization behind the 
> scenes?

Yes. But I don't think ozone does anything behind the scenes...

> I heard somewhere that serialization will not 
> offer good performance. I've read other messages that 
> were archived and it seems like it scaled and 
> performed well. So how does Ozone get around it. 

I personally tried to use pure serialization before switching to ozone. For about 5MB of data, it took one minute to create it.
The main problem are complex objects. By implementing your own serialization algorithm (see Java docs on http://java.sun.com for an explanation on how to do this) you can speed up things dramatically.
Now the performance of my app is ok, and it handles all data much better (because ozone forces you to a specific design).

> 2. I also read somewhere that you could very easily 
> get into performance issues with OODB systems. One of 
> the possible reasons that I could think of are,  
> trying to store and retrieve objects with complex 
> graphs( I mean too many nested objects ). So is there 
> a "best practices guide" or something like that, that 
> I could use to not get into trouble? Are there any 
> other factors that could result in poor performance? 

Yes, I had my first (and only for now) performance problem when the client tried to fetch 95 database objects to create a list. By moving this code into the server and sending the list as a whole to the client, my app got a speed boost from 30 sec to 0.7 sec.

andy


-- 
Description forthcoming.