Subject | Re: [firebird-support] Re: Our firebird database performance has come to a halt |
---|---|
Author | William L. Thomson Jr. |
Post date | 2005-12-15T19:16:32Z |
On Thu, 2005-12-15 at 15:38 -0200, Alexandre Benson Smith wrote:
connection speeds than to use autonegotiate. More so if you have a good
managed switch, and can do so on both ends. Should relate to more than
FB, but with allot of I/O auto-neg could become an issue, as stated.
I would assume in the case above setting it to a fixed full duplex would
have been better than half duplex. I would bet the difference came from
specifiying instead of negotiating speeds. Regardless of the speed or
duplex.
--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com
>If you have the ability to, it's almost always better to specify
> Nigel Weeks show me a tip that solved the issue:
> On the network configuration dialog turn off the auto-negotiating speed
> and set it up manually (take attention to the Full/Half duple point).
> Try playing with the settings and see how performs better for you, the
> problem in may case was that Windows Auto-negotiation choosed
> 100mpbs/Full Duplex, when I set it to Half duplex the speed comes back
> to normal.
connection speeds than to use autonegotiate. More so if you have a good
managed switch, and can do so on both ends. Should relate to more than
FB, but with allot of I/O auto-neg could become an issue, as stated.
I would assume in the case above setting it to a fixed full duplex would
have been better than half duplex. I would bet the difference came from
specifiying instead of negotiating speeds. Regardless of the speed or
duplex.
--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com