You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by ABOU LINA <am...@gmail.com> on 2006/05/08 11:56:26 UTC
auto-* in runtime ?
Hi,
Q1. We can change the value of auto-retrieve (-update) at the runtime ???
Q2. if you have a list of suggestion about how to improve perfermance ojb /
db2 , and methodologie of a best tuning
???
thx
Re: auto-* in runtime ?
Posted by ABOU LINA <am...@gmail.com>.
Thank you very much Armin for your reply.
we dont have a ojb plugin eclipse ??
On 5/8/06, Armin Waibel <ar...@apache.org> wrote:
>
> Hi,
>
> ABOU LINA wrote:
> > Hi,
> > Q1. We can change the value of auto-retrieve (-update) at the runtime
> ???
>
> All direct "object metadata" changes are global, thus all threads will
> see the changes immediately.
> Advanced user can define different object metadata profiles an can use
> these profiles in a per thread manner - see
> http://db.apache.org/ojb/docu/guides/metadata.html
>
>
> > Q2. if you have a list of suggestion about how to improve perfermance
> > ojb /
> > db2 , and methodologie of a best tuning
> > ???
>
> You can find some hints here
>
> http://db.apache.org/ojb/docu/guides/performance.html#What+are+the+best+settings+for+maximal+performance%3F
> Will add some more on next doc update (OJB 1.0.5).
>
> Most important are:
>
> The autocommit setting of used connections. For best performance
> it's recommended to set autocommit 'false' in the jdbc-driver or to use
> 'useAutoCommit="2"' setting in repository file database setting to avoid
> Connection.setAutoCommit(...) calls by OJB.
>
> Use of batch statements by enable batch mode (when supported by
> the DB) when insert/update/delete many objects of the same type (e.g.
> insert ProductGroup with 20 Article objects).
>
> PersistentField class implementation. See OJB.properties section
> 'PersistentFieldClass' to change the implementation.
>
> The used cache implementation.
>
> The JDBC driver settings (e.g. statement caching on/off).
>
> ConnectionFactory implementation / Connection pooling settings
> (e.g. prepared statement caching if the jdbc-driver doesn't support this
> feature). See connection pooling for more information.
>
> Used sequence manager implementation. See sequence manager for
> more information.
>
> PersistenceBroker pool size. See OJB.properties for more
> information.
>
> regards,
> Armin
>
>
> >
> > thx
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>
Re: auto-* in runtime ?
Posted by Armin Waibel <ar...@apache.org>.
Hi,
ABOU LINA wrote:
> Hi,
> Q1. We can change the value of auto-retrieve (-update) at the runtime ???
All direct "object metadata" changes are global, thus all threads will
see the changes immediately.
Advanced user can define different object metadata profiles an can use
these profiles in a per thread manner - see
http://db.apache.org/ojb/docu/guides/metadata.html
> Q2. if you have a list of suggestion about how to improve perfermance
> ojb /
> db2 , and methodologie of a best tuning
> ???
You can find some hints here
http://db.apache.org/ojb/docu/guides/performance.html#What+are+the+best+settings+for+maximal+performance%3F
Will add some more on next doc update (OJB 1.0.5).
Most important are:
The autocommit setting of used connections. For best performance
it's recommended to set autocommit 'false' in the jdbc-driver or to use
'useAutoCommit="2"' setting in repository file database setting to avoid
Connection.setAutoCommit(...) calls by OJB.
Use of batch statements by enable batch mode (when supported by
the DB) when insert/update/delete many objects of the same type (e.g.
insert ProductGroup with 20 Article objects).
PersistentField class implementation. See OJB.properties section
'PersistentFieldClass' to change the implementation.
The used cache implementation.
The JDBC driver settings (e.g. statement caching on/off).
ConnectionFactory implementation / Connection pooling settings
(e.g. prepared statement caching if the jdbc-driver doesn't support this
feature). See connection pooling for more information.
Used sequence manager implementation. See sequence manager for
more information.
PersistenceBroker pool size. See OJB.properties for more information.
regards,
Armin
>
> thx
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org