Hi All,Gavin also suggested to disable cglib optimization fully (there's a property to set in the hibernate.properties
I'm wondering if it's possible to do some generated-code at build time instead of generating the proxies at runtime. I'm using hibernate for a swing application and the majority of the initialization time is taken up by hibernate's initialization of the configuration object. (I've already sped up some of it using ideas from Andrea by using the Jade RealtimeParser and setting the xml validation to false) When I look at the profiler, it's always the same proxies that are being generated by cglib. Is there some way to persist some proxies at build time so that startup runtime time is shortened?
file). This gives you another small improvement.
Then, if you want some more, start up your virtual machine with the -Xverify:none flag to avoid
bytecode verification and test startup time with your class file in a jar, this reduces file attribute
verifications that are especially slow on ntfs filesystems (well, I guess the advantage is noticeable
on any file system that's not otimized for the "many small files" pattern like the linux reisersfs filesystem).
With these I can get my app startup time down to 2.5 seconds on a 1200 Mhz Duron with a quite old
ntfs filesystem, and it's cpu bound now (the other hibernate initializations according to the profiler).
Best regards Andrea Aime
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
