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.
New access path for faster first fetch with a good global time
Firstly, I don't know if it is possible. We can encounter this following performance issue : select on a big table with an order by. Depending on the statistics, we can have list prefetchs on an index. If the index is very big, we have to wait a long time to sort all the rids although it could be interesting to fetch so that the next steps in the program logic are executed during the rids sort.
We can disable the list prefetch to have fastly the first fetched rows but the total time of the request could increase. So the idea should to have a new access path to sort the rids in background but to fetch frequently some rows so that the program executes in parallel.
Do not place IBM confidential, company confidential, or personal information into any field.