While searching for various Data Warehouses, the analytical DB warehouse performs really poorly when it comes to actually Inserting values through a simple INSERT INTO.

As per Amazon the fastest way for Inserting to Redshift is through Dumping the Data into Amazon S3 Storage Servers and the using the COPY Command to transfer the Data. It is very fast (almost sub-second when doing this).

For regular Inserts Redshift seems to throttle my concurrent Inserts be it a Staging Copy of the Live Table. I had set up a concurrency of 5 inserts per second and got large delays in my Worker Queue.

Below are the Logs from my worker Queue benchmarking about 5 concurrent workers doing a single insert each into Redshift

09:53:17.045Z  INFO Titan-Runner: Push Completed in - 1.553s
09:53:17.045Z  INFO Titan-Runner: Push Completed for Document
09:53:17.457Z  INFO Titan-Runner: Push Started for Document
09:53:18.479Z  INFO Titan-Runner: Push Completed in - 2.91s
09:53:18.488Z  INFO Titan-Runner: Push Completed for Document
09:53:18.757Z  INFO Titan-Runner: Push Started for Document
09:53:19.786Z  INFO Titan-Runner: Push Completed in - 4.152s
09:53:19.787Z  INFO Titan-Runner: Push Completed for Document
09:53:19.896Z  INFO Titan-Runner: Push Started for Document
09:53:21.124Z  INFO Titan-Runner: Push Completed in - 5.693s
09:53:21.124Z  INFO Titan-Runner: Push Completed for Document
09:53:21.208Z  INFO Titan-Runner: Push Started for Document
09:53:22.424Z  INFO Titan-Runner: Push Completed in - 6.525s
09:53:22.424Z  INFO Titan-Runner: Push Completed for Document
09:53:22.476Z  INFO Titan-Runner: Push Started for Document
09:53:23.751Z  INFO Titan-Runner: Push Completed in - 7.427s
09:53:23.751Z  INFO Titan-Runner: Push Completed for Document
09:53:23.852Z  INFO Titan-Runner: Push Started for Document
09:53:25.064Z  INFO Titan-Runner: Push Completed in - 9.264s
09:53:25.064Z  INFO Titan-Runner: Push Completed for Document
09:53:25.170Z  INFO Titan-Runner: Push Started for Document
09:53:26.417Z  INFO Titan-Runner: Push Completed in - 10.039s
09:53:26.418Z  INFO Titan-Runner: Push Completed for Document
09:53:26.468Z  INFO Titan-Runner: Push Started for Document
09:53:27.757Z  INFO Titan-Runner: Push Completed in - 11.322s
09:53:27.757Z  INFO Titan-Runner: Push Completed for Document
09:53:28.039Z  INFO Titan-Runner: Push Started for Document
09:53:29.071Z  INFO Titan-Runner: Push Completed in - 12.692s
09:53:29.071Z  INFO Titan-Runner: Push Completed for Document
09:53:29.219Z  INFO Titan-Runner: Push Started for Document
09:53:30.353Z  INFO Titan-Runner: Push Completed in - 12.896s
09:53:30.353Z  INFO Titan-Runner: Push Completed for Document
09:53:30.407Z  INFO Titan-Runner: Push Started for Document
09:53:31.674Z  INFO Titan-Runner: Push Completed in - 12.917s
09:53:31.675Z  INFO Titan-Runner: Push Completed for Document
09:53:31.803Z  INFO Titan-Runner: Push Started for Document
09:53:33.013Z  INFO Titan-Runner: Push Completed in - 13.117s
09:53:33.014Z  INFO Titan-Runner: Push Completed for Document
09:53:33.067Z  INFO Titan-Runner: Push Started for Document
09:53:34.396Z  INFO Titan-Runner: Push Completed in - 13.188s
09:53:34.397Z  INFO Titan-Runner: Push Completed for Document
09:53:34.499Z  INFO Titan-Runner: Push Started for Document
09:53:35.747Z  INFO Titan-Runner: Push Completed in - 13.271s
09:53:35.747Z  INFO Titan-Runner: Push Completed for Document
09:53:36.083Z  INFO Titan-Runner: Push Started for Document
09:53:37.065Z  INFO Titan-Runner: Push Completed in - 13.213s
09:53:37.065Z  INFO Titan-Runner: Push Completed for Document
09:53:37.520Z  INFO Titan-Runner: Push Started for Document
09:53:38.425Z  INFO Titan-Runner: Push Completed in - 13.255s
09:53:38.425Z  INFO Titan-Runner: Push Completed for Document

The time starts increasing sequentially which makes it impossible to use Redshift for Real Time inserts.