We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Allow table compression to be disabled for DGTTs and CGTTs
In short: OLTP applications frequently encounter performance issues because DB2 enables table compression by default for all DGTTs / CGTTs.
Details from a real-time example:
When inserting 40K rows to a DGTT, it takes 2 seconds.
When we immediately insert another 40K rows to the same DGTT using the same INSERT statement, it takes 0.08 seconds.
This has nothing to do with caching. It is because compression is enabled by default for all DGTTs / CGTTs and this is the overhead of generating the compression dictionary.
DB2 only generates the compression dictionary if a certain amount of data is inserted (based on my tests, this was around 25K rows). The same applies to CGTTs.
What this means is that any proc which inserts > 25K rows (approx.) into a DGTT / CGTT will incur this significant overhead every time it is executed.
So procs that should take 0.08 seconds to execute will consistently take 2 seconds.
Most OLTP applications create small (and short-lived) temporary tables and therefore don't benefit from table compression. Having the ability to disable table compression will significantly improve query performance in many cases.
Do not place IBM confidential, company confidential, or personal information into any field.