lk1...@gmail.com> wrote:
> On 03/19/2013 01:18 AM, Rob Turpin wrote:
>
>> It's a simple table, primary key is an integer, with another column which
>> is integer. Although I do begin a transaction, do 1000 updates and then
>> commit.
>>
>> On Mon, Mar 18, 2013 at 11
A table with two columns, both integers, one column primary key. I iterate
and insert 100,000 values. Then do 100,000 random updates.
On Tue, Mar 26, 2013 at 4:30 AM, Dan Kennedy <danielk1...@gmail.com> wrote:
> On 03/26/2013 06:34 AM, Rob Turpin wrote:
>
>> Dan,
>>
>
as
well ask.
Thanks,
Rob
On Mon, Mar 18, 2013 at 12:20 PM, Rob Turpin <flax3...@gmail.com> wrote:
> I understand it's still under development, but was curious about the
> difference. I have commented out all of the debug defines and enabled
> -DNDEBUG=1 for the sqlite4 build.
&g
I understand it's still under development, but was curious about the
difference. I have commented out all of the debug defines and enabled
-DNDEBUG=1 for the sqlite4 build.
On Mon, Mar 18, 2013 at 12:00 PM, Simon Slavin <slav...@bigfraud.org> wrote:
>
> On 18 Mar 2013, at 5:28pm
It's a simple table, primary key is an integer, with another column which
is integer. Although I do begin a transaction, do 1000 updates and then
commit.
On Mon, Mar 18, 2013 at 11:36 AM, Dan Kennedy <danielk1...@gmail.com> wrote:
> On 03/19/2013 12:28 AM, Rob Turpin wrote:
>
>
I was running some performance tests for both sqlite3 and sqlite4 and have
a question about a difference in my numbers.
I'm running these on a Linux machine, so I enabled fdatasync for the
sqlite3 build.
I'm measuring the number of updates I can perform (updates per second),
here are the
So I'm assuming saving in memory databases isn't an option with sqlite4.
On Sat, Mar 2, 2013 at 5:58 AM, Richard Hipp <d...@sqlite.org> wrote:
> On Sat, Mar 2, 2013 at 5:52 AM, Rob Turpin <flax3...@gmail.com> wrote:
>
> > The backup API for sqlite3
>
The backup API for sqlite3
sqlite3_backup_init
sqlite3_backup_step
sqlite3_backup_finish
I can't find anything similar in sqlite4. Is there any, or plans for it?
Thanks,
Rob
___
sqlite-users mailing list
sqlite-users@sqlite.org
Richard,
I commented out SQLITE4_DEBUG and SQLITE4_MEMDEBUG and added -DNDEBUG=1.
That did the trick! More like 224,000 updates per second. Thanks for your
help
Rob
On Wed, Feb 27, 2013 at 5:47 AM, Richard Hipp <d...@sqlite.org> wrote:
> On Wed, Feb 27, 2013 at 3:24 AM, Rob Turp
I wrote up a test case to do some performance tests for the update
statement, and I'd thought I'd ask before probing around the code first.
I did some comparisons with SQLite3.
The update statement is like this:
update pk_sk set sk=? where pk=?
pk being the primary key.
Using the command line
7 PM, Rob Turpin wrote:
>
>> Yes.
>>
>
> Is it succeeding? Returning LSM_OK?
>
> Dan.
>
>
>
>
>> On Wed, Feb 20, 2013 at 3:14 AM, Dan Kennedy <danielk1...@gmail.com>
>> wrote:
>>
>> On 02/20/2013 05:07 PM, Rob Turpin wrote:
>>&g
Yes.
On Wed, Feb 20, 2013 at 3:14 AM, Dan Kennedy <danielk1...@gmail.com> wrote:
> On 02/20/2013 05:07 PM, Rob Turpin wrote:
>
>> I'm running some performance tests on the lsm storage engine, and an issue
>> has cropped up for me. I retrieved the sqlite4 code from the re
I'm running some performance tests on the lsm storage engine, and an issue
has cropped up for me. I retrieved the sqlite4 code from the repository
about a week ago.
I'm doing a simple single threaded test to see what kind of performance I
can get on write transactions. After completing the
13 matches
Mail list logo
