Parallel for in instant, Useful strategy ?

Parallel for in instant, Useful strategy ?

[Patrick]

I don't have any code written concerning this or even planned but I was just curious about something...

Sqlite is actually based on disk writes and not on sockets or some other IPC. It has a reputation for speed when utilized by a single user. Despite the usually frowned upon system calls, it is a well received library.

Assuming the user has a multicore computer, I am curious what would be the factor that slows the program, the overhead of creating multiple threads or the execution of a given single threaded program over the course of a few milliseconds.

I am not really suggesting a rewrite of sqlite but I am wondering, with the rise of multicores computers, whether commands might be better written as parallel programs.

Ada can interface with other languages but if Ada programs could be called as freestanding commands in tandem with other languages it might lower the barrier to entry for new users. Sqlite could be a template to work from.

Re: Parallel for in instant, Useful strategy ?

[Dmitry A. Kazakov]

On Fri, 25 Jan 2013 06:46:27 -0800 (PST), Patrick wrote:

> I am not really suggesting a rewrite of sqlite but I am wondering, with
> the rise of multicores computers, whether commands might be better written
> as parallel programs.

No. Multicore architecture is a shared-memory one. As such it has an
advantage only in the cases involving computations. In other cases (e.g.
persistence layer) the effect on performance is difficult to predict. It
can well be negative.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de