Never really played with JDO. SolarMetric's KODO JDO does byte-code
instrumentation. If this is done as a post-compile step (not runtime),
it should be reasonably fast.
The JDO paradigm abstracts too much away from relational db, and may be
unintuitive to use. I'd stick with Hibernate.
Try playing with serializing the configuration in-between restarts.
Hibernate does allow that. It will save some delay on start-up. Faster
hardware should also be considered.
I have around 60 mapped classes on AMD64 Ferrari 4000 laptop. After a
few restarts (that are needed for the OS to cache all used files in
memory), it is about 5 sec to re-load hibernate stuff.
-Serge
Dmitry Gusev wrote:
And what about JDO? Do you think it's too long on startup too?
2006/1/28, Sergei Dubov <[EMAIL PROTECTED]>:
he-he, try mapping anything non-trivial with RoR.
-Serge
gaz jones wrote:
actually i think its called ruby on rails :P
i have the same problem, hibernate takes a bit of time to startup on my
powerbook. have you tried the jetty6 plugin? once you have started it,
it
monitors for code changes so you dont have to keep stopping and
restarting
everything, not sure how that effects hibernate though as ive not got it
to
work with tapestry yet.. the latest release on the jetty website gives
you
(or me at least) exceptions when run with a tapestry project, but
apparently
if you download and build the latest snapshot these are fixed - ive not
had
a chance to try yet. it might speed development up for you...
On 1/28/06, Sergei Dubov <[EMAIL PROTECTED]> wrote:
Yep, there is one. It is called "AMD64 X2".
-Serge
Alexander Varakin wrote:
Hi,
Sorry if this is offtopic but I don't know where to ask.
I am using Hibernate for my current project but it has annoying long
startup
of about 10-15 sec on 1.5GHz PC.
I also tried iBATIS but it is also not very fast to come up.
Also it would be nice to have an option of dynamic generation of beans
and
mapping from database metadata. Not sure if this requirement is
implemented
by any OR tool in existence.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
