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.
Improve performance of writing data to Scenario DB
As per our analysis DOC uses JDBC "batch insert" method when writing data to Scenario Database. A much faster method would be "multiple row insert", which can also be done with JDBC.
The following link shows how to do it in Java. The author measured 100 milliseconds per record for "batch insert", compared to only 10 milliseconds per record for "multiple row insert". So it is about 10 times faster.
In our environment we also see 100 milliseconds per record to save it to Scenario DB. It would be great if DOC could achieve 10 milliseconds by using "multiple row insert".
Some of our scenarios are quite big with more than 2 million records. Writing the data takes 200 seconds. Users typically save a scenario to Scenario DB several times (initial load, solve, ...). Several minutes of waiting time for the users could be avoided, if saving scenarios would be much faster.
Overall we think that such a performance boost in communication with scenario database would be a valuable improvement of DOC. So we would like to suggest to you to have a close look at the possibility of "multiple row insert" and check whether DOC could make use of it in future releases.
Note: It is not a matter of system setup. Our system is fast in DOC terms. "Performance Test" function in "ODM Repository Administration" window rates our environment as follows: Load Quality Rating: 5 of 5 (Excellent) Save Quality Rating: 5 of 5 (Excellent)
Do not place IBM confidential, company confidential, or personal information into any field.