Subject | Re: [firebird-support] Slow initial connection |
---|---|
Author | Helen Borrie |
Post date | 2010-02-09T12:38:05Z |
At 10:25 PM 9/02/2010, you wrote:
btw, make sure you reboot the system after you disable SR on that partition.
./heLen
>Hi!Firewall? entry in the hosts file?
>
>I have a problem connecting to an old Firebird 1.0.3 Server.
>
>I use a connection string like the following "localhost:D:\someData.fdb".
>
>The connection takes approximately 10 secs. After the connection is made, everything works fast.
>
>Ok, I've read about the system restore issue, so i changed the file extension to *.fdb, I also checked accessing the database lying on a partition that the system restore is not even activated for. Still no luck!
>
>I'm using a Vista Home Edition and Firebird 1.0.3 installed as a service. I'm also only accessing a local firebird installation via tcp/ip. Any clues as to why the initial connect is so slow?
>The initial connection is also as slow when i use isql to connect.You would be well advised to check whether this happens only to the first connection, or whether it affects every connection. Try connecting with two or three instances of isql, for example. If indeed it is only the first connection that is copping this delay, then I'd look at what your anti-virus program is up to. The first connection causes the server to open the security database and the user database. Some AV programs check all files on open. You should never allow an AV program to operate on a database.
>Is there a known issue with this old releasePre-Fb 1.0.3 connection times had an inherent delay of 1 second per attachment. This *was* fixed in Fb 1.0.3. Other than that and the SystemRestore problem, I don't know of any.
btw, make sure you reboot the system after you disable SR on that partition.
> or must that come from some wrong configurationWith the default config you shouldn't have a wrong configuraton. Only you know what you configured to be non-default.
> or network problemsYou could try replacing localhost with 127.0.0.1, or the machine's own hostname or IP address, and see whether that makes any difference. Check the interbase.log, too, to see whether there might be any clues there. But, again, if you have a firewall rule missing for localhost/port 3050, you'd still need to fix that first.
>(Would be weired as I'm using the localhost)?It still has to be routed. It's not unknown for the loopback mechanism to be slower than connections from actual nodes.
./heLen