I believe it's related to your client code - In our use case we do easily 15k writes/sec in a cluster lower specced than yours.
Check that your jdbc connection has autocommit off so Phoenix can batch writes and that table has a reasonable UPDATE_CACHE_FREQUENCY ( more than 60000 ). On Thu, 12 Jul 2018, 21:54 alchemist, <alchemistsrivast...@gmail.com> wrote: > Thanks a lot for your help. > Our test is inserting new rows individually. For our use case, we are > benchmarking that we could be able to get 10,000 new rows in a minute, > using > a cluster of writers if needed. > When executing the inserts with Phoenix API (UPSERT) we have been able to > get up to 6,000 new rows per minute. > > We changed our test to perform the inserts individually using the HBase API > (Put) rather than Phoenix API (UPSERT) and got an improvement of more than > 10x. (up to 60,000 rows per minute). > > What would explain this difference? I assume that in both cases HBase must > grab the locks individually in the same way. > > > > -- > Sent from: http://apache-phoenix-user-list.1124778.n5.nabble.com/ >
