Subject | Re: Huge speed problem after changing CPU do Dual Core (FB1.5.3) |
---|---|
Author | Adam |
Post date | 2006-02-15T11:23:08Z |
--- In firebird-support@yahoogroups.com, Luis Madaleno <luis@...> wrote:
mask to lock it to a single processor in Firebird.conf (restart the
service after changing).
Slow to connect specifically isnt normally related to this. It is more
frequently
1) .gdb files on XP
2) Disk Shadowing on 2003.
I also wouldn't rule out in this case some network issue where it
takes a long time to resolve the hostname. It could be attempting to
resolve an address from a DNS server and timing out, particularly if
the delay is an identical time every time. Add an entry to the hosts
file to prevent this lookup.
Adam
>CPU
> Hi,
>
> I have this machine running Windows 2003 Server with FB1.5.3 SS.
> It had an AMD Opteron CPU with an ASUS SK8N, but I had to change the
> and mainboard to an AMD 64 X2 with an ASUS A8NE.connecting
> The network card also changed, but the rest is the same, including the
> OS instalation that restarted well with the new HW.
>
> But now all FB client apps take almost one minute to connect to the FB
> Server. It seems they keep searching for the server.
> After they load user complaint that the app is very very slow
> the first time to any table.connecting to
> Running the app at the server loads fast but takes a while
> any table for the first time.Is it bouncing between the CPUs? If so, you can set the CPUAffinity
>
> A tried to reinstall FB in many ways: 1.5.3 SS again, 1.5.2 SS again,
> 1.5.3 CS, and nothing changed.
>
> Need help real real soon please.
mask to lock it to a single processor in Firebird.conf (restart the
service after changing).
Slow to connect specifically isnt normally related to this. It is more
frequently
1) .gdb files on XP
2) Disk Shadowing on 2003.
I also wouldn't rule out in this case some network issue where it
takes a long time to resolve the hostname. It could be attempting to
resolve an address from a DNS server and timing out, particularly if
the delay is an identical time every time. Add an entry to the hosts
file to prevent this lookup.
Adam