Hi,

Var George wrote:

Armin

Of course for performance reason, if there is performance overhead
otherwise. I am just starting OJB evaluation so I am not an expert on OJB
internals yet. Not sure how/when repository metadata is parsed and cached in
OJB but for enterprise application with large-schema/large-tables the amount
of metadata will be quiet high and if its helps to boost run time
application performance then the startup cost is not that significant. Is
there any metadata initialization that's done late when individual objects
are queried?


After the first initialization (first use of MetadataManager) all metadata are in memory (default behaviour).
But it's also possible to read arbitrary repository files
at runtime and start OJB with an 'empty' or minimal repository
file (More see FAQ).


regards,
Armin

regards
Varughese George

On Tuesday, November 4, 2003, at 09:20 AM, Armin Waibel wrote:

Hi,

Var George wrote:

Is there a method to force OJB to fully initialize at startup (read all metadata, connection pool, etc) rather than incurring some of this cost when querying an object first time as illustrated in your test.

Sorry no, but why we should do this?


regards,
Armin

regards
Varughese George
On Tuesday, November 4, 2003, at 07:05  AM, Armin Waibel wrote:

Hi again,

as Thomas mentioned the test seems not fair,
because first time a PB instance start to work
behind the scenes some inital startup stuff
is done (read metadata, setup connection pool, ...)

I made some tests to demonstrate the
difference. I lookup three different
persons (thus no caching could be used)

result: eugen
591 ms
result: frido
10 ms
result: guido
10 ms

Thus to make the test more fair, lookup
a "dummy object" to allow complete startup
of both frameworks and then perform your test.

regards,
Armin




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



regards
Varughese George




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to