Subject | RE: [firebird-support] Windows 2003 oddities |
---|---|
Author | Donald Klopper |
Post date | 2004-01-25T09:44:27Z |
Check that HyperThreading is turned off on the P4 (?) BIOS.
This makes a huge difference on IB 6 on 2003 Server, and I believe has been
reported as a problem with Firebird also.
I worked with multiprocessor (2 processors only) Windows machines before,
and more often than I'd like the machine operates quicker when I remove the
second CPU. The overhead for managing memory / processes / concurrency on
the second CPU is just not worth it if the applications are not optimised
for it.
Hyperthreading, IMHO, is prone to the same limitations.
System Restore is not active on 2003 Server, and in any event just rename
your database to something other than .GDB on that platform. One of the
reasons for the security database getting a name name (security.fdb instead
of ISC4.GDB) is exactly because of the system restore issues on .GDB files
on XP, since the user / installer / administrator has no control over the
naming of the security database.
Donald Klopper
This makes a huge difference on IB 6 on 2003 Server, and I believe has been
reported as a problem with Firebird also.
I worked with multiprocessor (2 processors only) Windows machines before,
and more often than I'd like the machine operates quicker when I remove the
second CPU. The overhead for managing memory / processes / concurrency on
the second CPU is just not worth it if the applications are not optimised
for it.
Hyperthreading, IMHO, is prone to the same limitations.
System Restore is not active on 2003 Server, and in any event just rename
your database to something other than .GDB on that platform. One of the
reasons for the security database getting a name name (security.fdb instead
of ISC4.GDB) is exactly because of the system restore issues on .GDB files
on XP, since the user / installer / administrator has no control over the
naming of the security database.
Donald Klopper
> -----Original Message-----
> From: Milan Babuskov [mailto:albis@...]
> Sent: Friday, January 23, 2004 5:48 PM
> To: firebird-support@yahoogroups.com
> Subject: [firebird-support] Windows 2003 oddities
>
>
> Hi all,
>
> I have problem with connecting to Firebird 1.0.3 SS on Windows 2003
> server. It connects but slow. Once connected I can work without any
> problems. Everything works great. When I disconnect, it also takes 5-10
> seconds.
>
> I did shutdown VSS (shadowing) and db file is named zz.fdb. Also,
> Windows is "optimised for applications". I also added localhost to hosts
> file.
>
>
> Now what is interesting:
>
> When I connect with isql, and stay connected, I open the second dos
> prompt, and make another connection from it. It works instantly, like it
> should. Opening each new connection works fast. Disconnecting too. If I
> disconnect all clients, the first connection is slow again.
>
>
> This leads me to conclusion, that there is some problem when Firebird is
> reading the database file for the first time (attaching the database?)
> Once the database is attached, new connections are made really fast.
>
> Should I post my findings to the devel list?
>
> --
> Milan Babuskov
> http://fbexport.sourceforge.net
>
>
>
>
>
>
> Yahoo! Groups Links
>
> To visit your group on the web, go to:
> http://groups.yahoo.com/group/firebird-support/
>
> To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
>
> Your use of Yahoo! Groups is subject to:
> http://docs.yahoo.com/info/terms/
>
>