Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

Am 05.02.2015 um 20:21 schrieb Till Oliver Knoll: [...] Other links that I found seem to support that, that the underlying "scheduler" figures out the best read/write strategy, and any attempt by the application to implement that by itself would be counter-productive [...] One addition: If usin

Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

Hi Harri, Rainer, thanks for sharing your thoughts! Am 05.02.15 um 15:19 schrieb Harri Pasanen: > On 05/02/2015 14:44, Till Oliver Knoll wrote: >> >> Am 05.02.2015 um 14:25 schrieb Till Oliver Knoll >> mailto:till.oliver.kn...@gmail.com>>: >> >>>... I am really >> just interested in whether concu

Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

From: Till Oliver Knoll > Am 05.02.2015 um 14:25 schrieb Till Oliver Knoll: > > ... > > > > Does it make sense to guarantee/enforce "sequential (exclusive) > > access to the harddisk" on application level, or would I > > re-invent functionality already present in the underlying > > OS/disk driver

Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

Am 05.02.2015 um 14:44 schrieb Keith Gardner : Thanks for the quick reply! >> ... >> Specifically I have the following scenario in mind: "batch image >> conversion". ... > > Have you looked at ThreadWeaver > (http://api.kde.org/frameworks-api/frameworks5-apidocs/threadweaver/html/index.html)?

Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

On 05/02/2015 14:44, Till Oliver Knoll wrote: Am 05.02.2015 um 14:25 schrieb Till Oliver Knoll mailto:till.oliver.kn...@gmail.com>>: ... Does it make sense to guarantee/enforce "sequential (exclusive) access to the harddisk" on application level, or would I re-invent functionality already

Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

> > Does it make sense to guarantee/enforce "sequential (exclusive) access to > the harddisk" on application level, or would I re-invent functionality > already present in the underlying OS/disk driver (and maybe even sacrifice > performance)? > It depends on the task at hand. If you know you are

Re: [Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

> Am 05.02.2015 um 14:25 schrieb Till Oliver Knoll > : > > ... > > Does it make sense to guarantee/enforce "sequential (exclusive) access to the > harddisk" on application level, or would I re-invent functionality already > present in the underlying OS/disk driver (and maybe even sacrifice >

[Interest] [Semi OT] Concurrent (multi-threaded) read/write disk IO?

Hi all, This is somewhat unrelated to Qt, but I hope one or another has stumbled over this and can share some thoughts. Does it make sense to guarantee/enforce "sequential (exclusive) access to the harddisk" on application level, or would I re-invent functionality already present in the underl