Hi,
About read performance you can use :
1. getIterator instead of getCollection
2. or use proxy solution
3. using the cach of ojb

another thing but i don't know how can we do it in OJB ; when OJB prepare a
statement (for read) by default he make SELECT * FROM ... so i think if we
have
a posibility to specify only fields that's we need instead of (*) we got a
good result at performance level in reading.





On 2/10/06, Milisic Aleksandar <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I was just wondering if somebody could tell me what
> are the general techniques used when performing writes
> and reads to optimize the performance (speed wise) of
> OJB?
> Or is anything said about it in the documentation (I
> am having trouble finding it)?
>
>
> The reason I am asking is because I am doing some
> profiling comparing OJB code with java sql and the OJB
> code seems to be much slower for both reads and
> writes, so I wanted to know how I can optimize it.
>
> Thank you.
>
>
>
> ____________________________________________________
> Do you Yahoo!?
> Messenger 7.0: Free worldwide PC to PC calls
> http://au.messenger.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to