Re: [sqlite] about the apparently arriving soon "threads"

Hi James, You're right : my example is indeed a "4 independant process" rather than "4 threads in the same process". The job I need to do is unchanged : transform a big input table in a big output table. I hope that SQlite improvements will allow us to approach this "2x" (or more) boost in the

Re: [sqlite] about the apparently arriving soon "threads"

On Wed, 9 Apr 2014 19:07:27 +0200 big stone wrote: > Threading Plumbery is managed via DOS ".bat commands, as below : > - a "main.bat" dos command : > . pre-clears the 4 "ok finished" files, > . launch the 4 threads, > . then check every 2 seconds that all "ok finished"

Re: [sqlite] about the apparently arriving soon "threads"

Hi Simon, About my test : - principal input fact file is 220 000 line of 5 fields ( 7 389 Ko in Utf-8 on a windows pc) - other files are 65 Ko - initial and final data is on a 7200 rpm rotating disk, - sqlite database(s), one per thread, is in ":memory:". Threading Plumbery is managed via DOS

Re: [sqlite] about the apparently arriving soon "threads"

>On Tue, Apr 8, 2014 at 11:00 PM, big stone wrote: >> Hi, >> >> I did experiment splitting my workload in 4 threads on my cpu i3-350m >to >> see what are the scaling possibilities. >> >> Timing : >> 1 cpu = 28 seconds >> 2 cpu = 16 seconds >> 3 cpu = 15 seconds >> 4 cpu = 14

Re: [sqlite] about the apparently arriving soon "threads"

On Tue, Apr 8, 2014 at 11:00 PM, big stone wrote: > Hi, > > I did experiment splitting my workload in 4 threads on my cpu i3-350m to > see what are the scaling possibilities. > > Timing : > 1 cpu = 28 seconds > 2 cpu = 16 seconds > 3 cpu = 15 seconds > 4 cpu = 14 seconds >

Re: [sqlite] about the apparently arriving soon "threads"

On 8 Apr 2014, at 8:00pm, big stone wrote: > I did experiment splitting my workload in 4 threads on my cpu i3-350m to > see what are the scaling possibilities. > > Timing : > 1 cpu = 28 seconds > 2 cpu = 16 seconds > 3 cpu = 15 seconds > 4 cpu = 14 seconds > > Analysis :

Re: [sqlite] about the apparently arriving soon "threads"

Hi, I did experiment splitting my workload in 4 threads on my cpu i3-350m to see what are the scaling possibilities. Timing : 1 cpu = 28 seconds 2 cpu = 16 seconds 3 cpu = 15 seconds 4 cpu = 14 seconds Analysis : - sqlite is such a small foot-print in memory, it is really scaling well with the

Re: [sqlite] about the apparently arriving soon "threads"

On Sat, Apr 5, 2014 at 9:16 AM, big stone wrote: > Hello, > > I see the "threads" branch of fossil has a lot of activity and seems close > to be finalized. > No, it still has a long way to go. > > Will it be activated by default on the downloadable executable for windows

[sqlite] about the apparently arriving soon "threads"

Hello, I see the "threads" branch of fossil has a lot of activity and seems close to be finalized. Will it be activated by default on the downloadable executable for windows ? Will it apply to parallelisable CTE expression ? Will it be possible from 1 sqlite.exe command line (or 1 python