🚀 go-pugleaf

There is an Interbase issue in Windows 2003 Server if either Hyperthreading
is enabled or there are multiple physical CPU's installed.  A work-around is
to pin IB to a single (real or virtual) processor. This was addressed in IB
7.1.

Windows 2003 Server does not have System File Protection like Windows XP; in
2003 Server, there's Volume Shadow Copy, which is similar, but not the same
as SFP in XP.  As far as I know, Volume Shadow Copy does not work on an
extension-by-extension basis.

Dan


"Bill Todd" <no@no.com> wrote in message
news:4166e414@newsgroups.borland.com...
> There is no performance penalty for running on Win2003 as long as you
> avoid the performance penalty caused by system restore trying to backup
> files with the .gdb extension.
>
> The performance penalty occurrs when the O/S swaps the Ib process from
> one processor to another. It makes no difference whether the processors
> are virtual or physical. It is the context switch that takes the time.
>
> -- 
> Bill (TeamB)
> TeamB cannot answer questions received via email
>
> Marcelo Carvalho wrote:
>
> > But will the performance be reduced in single processor and non HT
> > machines, as happens to Win2003 Server?
> >
> >                Marcelo Carvalho
> >
> > "Bill Todd" <no@no.com> escreveu na mensagem
> > news:4166d077$1@newsgroups.borland.com...
> > > Both.
> > >
> > > -- 
> > > Bill (TeamB)
> > > TeamB cannot answer questions received via email
> > >
> > > Marcelo Carvalho wrote:
> > >
> > >> So you mean that in Win XP the problem occurs only in HT machines,
> > >> right?  Or just real multi CPU machines?