-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Due to the lack of support for hibernate.jdbc.batch_size in DB2 and Sybase:
http://www.hibernate.org/120.html#A6
We have removed the benefit of JDBC batching processing on all of our databases. For example, some upgrade tasks that do batch inserts/updates/deletes could run faster with batching enabled.
This does not have to be the case. We can apply the batch setting on a per dialect basis by updating:
com.atlassian.config.db.HibernateConfig#getHibernateProperties
We can determine the dialect by querying applicationConfig.
- relates to
-
CONFCLOUD-15347 Turn on batch processing in hibernate for databases that support it
- Closed
[CONFSERVER-15347] Turn on batch processing in hibernate for databases that support it
Workflow | Original: JAC Suggestion Workflow 4 [ 3575306 ] | New: JAC Suggestion Workflow 3 [ 4326544 ] |
Workflow | Original: JAC Suggestion Workflow 2 [ 3172823 ] | New: JAC Suggestion Workflow 4 [ 3575306 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3033211 ] | New: JAC Suggestion Workflow 2 [ 3172823 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2534652 ] | New: JAC Suggestion Workflow [ 3033211 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 2295817 ] | New: Confluence Workflow - Public Facing v4 [ 2534652 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 - TEMP [ 2190936 ] | New: Confluence Workflow - Public Facing v3 [ 2295817 ] |
Workflow | Original: Confluence Workflow - Public Facing v3 [ 1925727 ] | New: Confluence Workflow - Public Facing v3 - TEMP [ 2190936 ] |
Workflow | Original: Confluence Workflow - Public Facing v2 [ 1755257 ] | New: Confluence Workflow - Public Facing v3 [ 1925727 ] |
Description |
Original:
Due to the lack of support for hibernate.jdbc.batch_size in DB2 and Sybase:
http://www.hibernate.org/120.html#A6 We have removed the benefit of JDBC batching processing on all of our databases. For example, some upgrade tasks that do batch inserts/updates/deletes could run faster with batching enabled. This does not have to be the case. We can apply the batch setting on a per dialect basis by updating: com.atlassian.config.db.HibernateConfig#getHibernateProperties We can determine the dialect by querying applicationConfig. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-15347]. {panel} Due to the lack of support for hibernate.jdbc.batch_size in DB2 and Sybase: http://www.hibernate.org/120.html#A6 We have removed the benefit of JDBC batching processing on all of our databases. For example, some upgrade tasks that do batch inserts/updates/deletes could run faster with batching enabled. This does not have to be the case. We can apply the batch setting on a per dialect basis by updating: com.atlassian.config.db.HibernateConfig#getHibernateProperties We can determine the dialect by querying applicationConfig. |
Link |
New:
This issue relates to |