phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <>
Subject Re: Improve upsert performance - JDBC
Date Thu, 20 Mar 2014 04:44:21 GMT
Best would be to track how many rows you've received and commit once a
threshold is reached (as it sounds like the rate at which objects are
received varies pretty greatly).

On Wed, Mar 19, 2014 at 6:12 PM, Manthosh Kumar T <>wrote:

> Hi James,
>                  Thanks. I'm using Phoenix with Storm. Say I need to store
> objects in Phoenix from a source. The rate at which this source emits the
> object ranges from 4000/second to 4/second. Another application needs to
> read from this table concurrently and needs to know the total objects
> received till that time. That's why I had set auto commit as true. So to
> improve performance, is it efficient to perform commit based on time (say
> for every second)?
> On 17 Mar 2014 22:24, "James Taylor" <> wrote:
>> Hi Manthosh,
>> Probably not a lot you can do. If it's the same upsert statement, you can
>> cache the PreparedStatement to avoid the parse cost (but I doubt that'll
>> help).
>> Any reason why you can't turn auto commit off and commit in batches?
>> Thanks,
>> James
>> On Mon, Mar 17, 2014 at 5:39 AM, Manthosh Kumar T <>wrote:
>>> Hi All,
>>>          Currently when I upsert values via JDBC, each upsertion takes
>>> 14-20 ms on an average. Auto commit is set to true. Is there a way to
>>> improve this without batch insert?.
>>> --
>>> Cheers,
>>> Manthosh Kumar. T

View raw message