Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Sep 26, 2017

Better performance of Java table routines

The existing Db2 interface for developing table functions in Java programming language is not designed for performance, because:
(a) It requires a separate native (JNI, e.g. Java-to-C) call for setting each field value for each output row
(b) It implies a separate C-to-Java call for each output row.
Java-to-C and C-to-Java calls are very expensive, and although it is not possible to completely avoid them, one of the important targets for performance tuning is to minimize the number of such calls.
The possible approach to minimize the expensive calls is to create the alternate to the current base class, with the following improvements:
(1) Change all set(...) methods to non-native final, caching the data in some Java data structure (Map or ArrayList)
(2) Change all the get*() methods to non-native final, making the necessary data available in the Java data structures at the first call (e.g. if the data is not available, call the JNI method, otherwise use the cached copy).
(3) Add the method nextRow(), which will back the current row of values to some data structure (ByteArrayOutputStream?). If this structure exceeds the limit, push the pack of rows to private JNI method, which will send them for processing to the Db2 engine.
With those changes, small output tables in most cases will require only three expensive calls:
- the instantiation of UDF implementation class;
- actual call to the UDF implementation method;
- final call to the internal method returning the pre-packed set of rows.