1, will be so one-to-many relationship set to lazy in the true
2, modified hibernate.properties, an increase of the following two sentences:
hibernate.jdbc.fetch_size = 50
hibernate.jdbc.batch_size = 100
3, the pool adjustment WebLogic
4, using Hibernate to provide the CGLIB Proxy mechanism to enable many-to-one relationship between the sub-objects can also be lazy initialization
(However, I found in debug window there will be sub-object from SQL statements, but the speed really fast).
5, the Cache using Hibernate to provide a mechanism to use the Cache object key
1. Great Eastern. If a lot of one-to-many and many-to-one relationship. It will definitely affect the performance, I am just learning Hibernate have this intuition, we did not use one-to-many and many-to-one relationship. but as to the operation of the same SQL table identifier of the relationship.
2. If the super-system, and ultimately must generate HTML documents. Is the data to update the database automatically generate a HTML document. The majority of users are in the read-only state. In the read-only state to show only HTML files, save a lot of resources.
3. CHACHE table technology used to access the records of high CACHE automatically referred to the table.







