This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
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/sec When we started using Redshift connector for performing updates, the performance was pretty slow - 2 rows/sec With these performances, ...
Do not place IBM confidential, company confidential, or personal information into any field.