Redshift COPY is immensely faster than trying to do insert statements. I did some rough testing of inserting data using INSERT and COPY and COPY is vastly superior to the point that if speed is at all an issue to your process you shouldn't even consider using INSERT.
On Mon, Apr 24, 2017 at 11:07 AM, Afshin, Bardia < bardia.afs...@capitalone.com> wrote: > I wanted to reach out to the community to get a understanding of what > everyones experience is in regardst to maximizing performance as in > decreasing load time on loading multiple large datasets to RedShift. > > > > Two approaches: > > 1. Spark writes file to S3, RedShift COPY INTO from S3 bucket. > > 2. Spark directly writes results to RedShfit via JDBC > > > > JDBC is known for poor performance, and RedShift (wihtout any provided > examples) claims you can speed up loading from s3 buckets via different > queues set up in your RedShift Workload Management. > > > > What’s the communities experience with desiging processes which large > datasets are needed to be pushed into RedShfit and doing it in minimal time > taken to load the data to RedShift? > > ------------------------------ > > The information contained in this e-mail is confidential and/or > proprietary to Capital One and/or its affiliates and may only be used > solely in performance of work or services for Capital One. The information > transmitted herewith is intended only for use by the individual or entity > to which it is addressed. If the reader of this message is not the intended > recipient, you are hereby notified that any review, retransmission, > dissemination, distribution, copying or other use of, or taking of any > action in reliance upon this information is strictly prohibited. If you > have received this communication in error, please contact the sender and > delete the material from your computer. > -- Regards, Matt Data Engineer https://www.linkedin.com/in/mdeaver http://mattdeav.pythonanywhere.com/
