30.05.2017 19:32, Leyne, Sean wrote:
Async/Overlapped IO allows for IO on any number of file blocks (aka pages)
without limit to their locations, consecutive or not.
You words "single operation for any storage device" make me think that
you are referring to a single OS call. There is no
> > Async/Overlapped IO allows for IO on any number of file blocks (aka pages)
> without limit to their locations, consecutive or not.
>
>You words "single operation for any storage device" make me think that
> you are referring to a single OS call. There is no such API in "only platform
>
29.05.2017 23:45, Leyne, Sean wrote:
Vlad,
- Asynchronous File I/O
It is not really asynchronous as it waits for the completion of
every single IO request.
True, but it allows the storage controller to decide the best order in which
to perform the operations...
Order of what ?
Vlad,
> >>> - Asynchronous File I/O
> >>
> >> It is not really asynchronous as it waits for the completion of
> >> every single IO request.
> >
> > True, but it allows the storage controller to decide the best order in which
> to perform the operations...
>
>
>Order of what ? IO
26.05.2017 2:17, Leyne, Sean пишет:
- Asynchronous File I/O
It is not really asynchronous as it waits for the completion of every
single IO
request.
True, but it allows the storage controller to decide the best order in which to
perform the operations...
Order of what ? IO
> > - Asynchronous File I/O
>
>It is not really asynchronous as it waits for the completion of every
> single IO
> request.
True, but it allows the storage controller to decide the best order in which to
perform the operations...
> Also, note, it completely disables file system
25.05.2017 22:18, Leyne, Sean wrote:
What's SUPERSERVER_V2 in the code?
My review of the code (back in 2003, see attached) found the following:
- Asynchronous File I/O
It is not really asynchronous as it waits for the completion of every single
IO request. Also, note, it completely
25.05.2017 18:53, Adriano dos Santos Fernandes wrote:
What's SUPERSERVER_V2 in the code?
Old attempt by Borland to implement some features that can be utilized
by a properly threaded SuperServer.
Will it be used some day?
Will it be removed some day?
We preserve it as a reference. Some
Forgot to attachment...
> -Original Message-
> From: Leyne, Sean [mailto:s...@broadviewsoftware.com]
> Sent: Thursday, May 25, 2017 3:19 PM
> To: For discussion among Firebird Developers de...@lists.sourceforge.net>
> Subject: Re: [Firebird-devel] SUPERSERVER_V2
&
> What's SUPERSERVER_V2 in the code?
My review of the code (back in 2003, see attached) found the following:
- Asynchronous File I/O
- PreFetch Data Pages (i.e. statement is a natural scan so read-ahead in the
file...)
- Defer Header Page Write (i.e. reduce the number of times that the header
On 03/30/15 16:16, marius adrian popa wrote:
Seems that it is not used for years
https://github.com/FirebirdSQL/core/search?utf8=%E2%9C%93q=SUPERSERVER_V2
Jim removed it in Vulcan
Please do not cleanup it.
--
Dive
No problem this is why i asked
related old thread with cleanup question
https://sourceforge.net/p/firebird/mailman/message/15759466/
On Mon, Mar 30, 2015 at 4:31 PM, Alex Peshkoff peshk...@mail.ru wrote:
On 03/30/15 16:16, marius adrian popa wrote:
Seems that it is not used for years
12 matches
Mail list logo
