info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Access slow on TCP/IP fast on IPX/SPX
1 view
Skip to first unread message
Tom van der Woude
Mar 22, 2001, 5:52:22 AM3/22/01
to
Why is MS Access 97/2000 so slow on TCP/IP compared to IPX/SPX which runs 3x -
10x faster.
My clients uses a server with Access database 100Mb+ and Access front-end on
clients W95 and W98.
When using IPX/SPX protocol respons time is acceptable, but when using TCP/IP as
protocol the respons times are not acceptable at all.
But as I installed router software on the server, and some clients want to access
the internet through this software, TCP/IP seesm to be the default protocol for
these clients.
10x faster.
My clients uses a server with Access database 100Mb+ and Access front-end on
clients W95 and W98.
When using IPX/SPX protocol respons time is acceptable, but when using TCP/IP as
protocol the respons times are not acceptable at all.
But as I installed router software on the server, and some clients want to access
the internet through this software, TCP/IP seesm to be the default protocol for
these clients.
To be explicit there is no SQL-server installed, only fileserver NT4-SP6
Physical network is allright, no hardware problems, nor any driver problems.
Basic network speed on TCP/IP is perfect, but not with Access !!!
regards, Tom
Andrew Johnson
Mar 22, 2001, 7:12:41 AM3/22/01
to
My company has done quite a bit of work on TCP/IP issues like this and it
appears that it is the way MS have implemented TCP/IP and Delayed ACK's.
Basically an Ack is sent on every even packet but if an odd number of
packets is recieved then the system waits a default 200ms to timeout (since
no ack is sent on an odd packet). Apparently you can configure the timeout
with TCPDelAckTicks but we cannot get it to work on our NT4 setup - we are
waiting to hear from MS on how to implement this key.
appears that it is the way MS have implemented TCP/IP and Delayed ACK's.
Basically an Ack is sent on every even packet but if an odd number of
packets is recieved then the system waits a default 200ms to timeout (since
no ack is sent on an odd packet). Apparently you can configure the timeout
with TCPDelAckTicks but we cannot get it to work on our NT4 setup - we are
waiting to hear from MS on how to implement this key.
For a guess Access generates lots of odd numbered packet bursts - hence why
it works with IPX ok.
Make sense?
Andy.
Tom van der Woude <it-su...@systronix.nl> wrote in message
news:0cc801c0b2be$2c7a3230$9ae62ecf@tkmsftngxa02...
netw...@911networks.com
Apr 8, 2001, 7:18:35 PM4/8/01
to
See: http://www.911networks.com > Networks > Slow
> Why is the computer is slow when sending data
but receive at full speed?
> Why is the computer is slow when sending data
but receive at full speed?
##############################################
http://www.911networks.com
Real Solutions to Real Windows and Networking Problems
Covers: Networks, Windows 95, Windows 98, Windows NT
Free weekly newsletter
##############################################
John S. Giltner, Jr.
Apr 8, 2001, 8:41:31 PM4/8/01
to Andrew Johnson
TCPDelAckTicks is only valid in CE and 2000, it does not work in NT.
Windows does not delay on just odd number packets, it is every other
packet, there is a difference.
Windows does not delay on just odd number packets, it is every other
packet, there is a difference.
0 new messages