seperation of process

[al0]

What may help you to improve startup time is dynamic-insert=true and dynamic-update=true in your class mappings. The problem is that these settings can not be specified globally and as well are not inherited, so they shall be specified individually on each class, subclass and joined-subclass element in your mappings.

In the presence of these settings Hibernate does not try to generate and cache for future use insert and update statements for each and every table in mapping right on startup, but does it only when statement has to be used (in which case only affected columns are included in the statement). Some times it is good for performance, sometimes -bad, but anyhow for big schemas startup time is be greatly reduced.

Another possible optization is to mark all immutable classes (if any) as such (mutable="false"). "Immutable" in this context means that your application never update or delete objects of this classes in/from DB.

Regards,
Oleksandr

Hmmm, I would like to do the same.....
I 'll give u info about our data model may be u can give me some pointers of how to go about this.
Our data model is having around 2000+ tables. the associations are also closely knitted. For some reasons i must do the entire data loading with which i can't avoid any objects..... is there a way we can dynamically load the objects only on demand and the same for the the associated objects also...

Sudha

[karldmoore]

As has already been said, it would be useful to narrow down exactly what is taking the time. Presumably it is your LocalSessionFactoryBean. It does sound like you want to allow different parts of your context to be restarted and others to be left alone. Have you looked into OSGi?

[sudha_parimala]

Hi Karl,
I am trying to look into the actual content that's loading time. meanwhile i'll also look into OSGi. Tks for your valuable suggestions. I'll keep posing my findings. pls let me know if you have any other suggestions.

Regards

[karldmoore]

I am trying to look into the actual content that's loading time.

That would be useful to know, it does sound like an awful long time to startup.

meanwhile i'll also look into OSGi.

I'm not sure if it will help, but it does seem like you potentially want to take part of the application down and leave the rest running. This could be an interesting fit.

Tks for your valuable suggestions. I'll keep posing my findings. pls let me know if you have any other suggestions.

Looking forward to seeing what you come back with!