[ https://issues.apache.org/jira/browse/BEAM-4049?focusedWorklogId=92466&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-92466 ]
ASF GitHub Bot logged work on BEAM-4049: ---------------------------------------- Author: ASF GitHub Bot Created on: 19/Apr/18 09:22 Start Date: 19/Apr/18 09:22 Worklog Time Spent: 10m Work Description: adejanovski commented on issue #5112: [BEAM-4049] Improve CassandraIO write throughput by performing async queries URL: https://github.com/apache/beam/pull/5112#issuecomment-382669301 > BTW, @adejanovski if you want more sync than the PR comments, we can sync up on slack (the-asf.slack.com) we are in the same timezone, and even same country :) Sure thing, but is the ASF slack opened to anyone or just members of the ASF ? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 92466) Time Spent: 5h 10m (was: 5h) > Improve write throughput of CassandraIO > --------------------------------------- > > Key: BEAM-4049 > URL: https://issues.apache.org/jira/browse/BEAM-4049 > Project: Beam > Issue Type: Improvement > Components: io-java-cassandra > Affects Versions: 2.4.0 > Reporter: Alexander Dejanovski > Assignee: Alexander Dejanovski > Priority: Major > Labels: performance > Time Spent: 5h 10m > Remaining Estimate: 0h > > The CassandraIO currently uses the mapper to perform writes in a synchronous > fashion. > This implies that writes are serialized and is a very suboptimal way of > writing to Cassandra. > The IO should use the saveAsync() method instead of save() and should wait > for completion each time 100 queries are in flight, in order to avoid > overwhelming clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)