Keith Medcalf Sent Saturday, January 04, 2020 3:29 PM
>So I conclude that SERIALIZED/MULTITHREAD makes very little difference
>and that MEMSTATUS ON/OFF makes a huge difference. Since the
That's a potentially very useful observation! Is any of this available to JDBC
users?
Erik
nticipated traffic volume.
>-Original Message-
>From: sqlite-users On
>Behalf Of Doug
>Sent: Saturday, 4 January, 2020 10:42
>To: 'SQLite mailing list'
>Subject: Re: [sqlite] FW: Questions about your "Performance Matters" talk
>re SQLite
>
>Thanks, Jen
> -Original Message-
> From: sqlite-users
> On Behalf Of J Decker
> Sent: Saturday, January 04, 2020 4:11 AM
>
> Could wish there was a way to
> pause execution without giving up execution context...
What about?
for (i=1000; i--; i>0);
___
te mailing list
> Cc: em...@cs.umass.edu; curtsin...@grinnell.edu
> Subject: Re: [sqlite] FW: Questions about your "Performance
> Matters" talk re SQLite
>
>
> > On Jan 2, 2020, at 11:54 AM, Doug wrote:
> >
> > I know there has been a lot of talk about
On Sat, Jan 4, 2020 at 2:59 AM Howard Chu wrote:
> Keith Medcalf wrote:
> >
> > Indeed turning off memstatus leads to a 500% (from ~3s to ~0.5s)
> performance increase.
> > Changing the threading mode or the indirection level of the mutexes
> calls seems to have no significant effect.
> >
> Goes
Keith Medcalf wrote:
>
> Indeed turning off memstatus leads to a 500% (from ~3s to ~0.5s) performance
> increase.
> Changing the threading mode or the indirection level of the mutexes calls
> seems to have no significant effect.
>
Goes to show - publishing benchmark results without
> On Jan 2, 2020, at 11:54 AM, Doug wrote:
>
> I know there has been a lot of talk about what can and cannot be done with
> the C calling interface because of compatibility issues and the myriad set of
> wrappers on various forms. I’m having a hard time letting go of a possible
> 25%
Well, I told you I'm getting SQLITE_MISUSE so that kinda answers your side
question?
I am only interested in this topic for the performance gain so quoted.
I need to create a personal test case(my use model) to verify these
statements.
Querying the config state is helpful for a dll wrapped
On 1/3/20, sky5w...@gmail.com wrote:
> Is there a query function for these and other config settings?
> I see no sqlite3_config_get() in sqlite3.h.
There is no query function for the SQLITE_CONFIG_MEMSTATUS setting.
--
D. Richard Hipp
d...@sqlite.org
On Friday, 3 January, 2020 11:32, sky5w...@gmail.com wrote:
> Is there a query function for these and other config settings?
> I see no sqlite3_config_get() in sqlite3.h.
No. There are config options to get specific config data where that might be
useful.
Otherwise, you simply set the
Is there a query function for these and other config settings?
I see no sqlite3_config_get() in sqlite3.h.
On Fri, Jan 3, 2020 at 11:36 AM Keith Medcalf wrote:
> On Friday, 3 January, 2020 09:30, sky5w...@gmail.com wrote:
>
> >I get SQLITE_MISUSE when attempting
>
> Indeed turning off memstatus leads to a 500% (from ~3s to ~0.5s)
performance increase.
> Changing the threading mode or the indirection level of the mutexes calls
seems to have no significant effect.
That is quite significant.
Looking at the code, it seems the mutex requirement is mostly for
On Friday, 3 January, 2020 09:30, sky5w...@gmail.com wrote:
>I get SQLITE_MISUSE when attempting
>sqlite3_config(SQLITE_CONFIG_MEMSTATUS, 0);
>immediately after opening a db connection?
>My connection has THREADSAFE = 1.
That is correct. You must configure the library before it is initialized,
riginal Message-
> >From: sqlite-users On
> >Behalf Of Richard Hipp
> >Sent: Thursday, 2 January, 2020 16:00
> >To: SQLite mailing list
> >Subject: Re: [sqlite] FW: Questions about your "Performance Matters" talk
> >re SQLite
> >
> >On 1/2
anticipated traffic volume.
>-Original Message-
>From: sqlite-users On
>Behalf Of Richard Hipp
>Sent: Thursday, 2 January, 2020 16:00
>To: SQLite mailing list
>Subject: Re: [sqlite] FW: Questions about your "Performance Matters" talk
>re SQLite
>
>On 1/2
On 1/2/20, Barry Smith wrote:
> One thing that really stands is “creates 64 threads that operate on
> independent tables in the sqlite database, performing operations that should
> be almost entirely independent.”
>
Looking at the main.c file
One thing that really stands is “creates 64 threads that operate on independent
tables in the sqlite database, performing operations that should be almost
entirely independent.”
But that’s not how SQLite works - at least not when writing data. SQLite takes
a lock on the entire database, there
I asked for some information from Emery Berger about his video talk on
performance where he said they got a 25% improvement in SQLite performance.
Here is the reply I got back.
I know there has been a lot of talk about what can and cannot be done with the
C calling interface because of
18 matches
Mail list logo
