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.
We at NYL planning to move from On Prem to Cloud environment. We did a multiple testings with the help of IBM Support team and noticed that the Redshift loads using Redshift connector/JDBC connector as dead slow.
This will impact all of our Target load jobs in NYL EDM environment.
Currently Redshift connector is taking 35 mins for 1 million records to insert and going at 2 rows/sec for updates.
Proposed Idea/Solution - After the data is written to the S3 connector, we request to have an option to load that data using native S3 copy command into Redshift database. This should work for both Insert and Updates
Redshift connector slowness for Inserts, Updates and Deletes
When we started using Redshift connector for performing inserts, the performance was pretty slow - 470 rows/secWhen we started using Redshift connector for performing updates, the performance was pretty slow - 2 rows/secWith these performances, we...
Do not place IBM confidential, company confidential, or personal information into any field.