E
EEcanes
We are in the early stages of a Microsoft Project Server 2003
implementation. In reviewing the Project Server Configuration 2003
Planning Guide, it states "...an acceptable WAN performance means that
latency should not exceed 30ms."
Based on this statement, we are strongly considering the use of
Windows Terminal Server. However, we're wondering how slow performance
would actually be when opening/publishing schedules over a WAN whose
latency is say between 45 to 60ms.
Understanding we can validate performance speculations using a test
bed (we just don't have the gear right now), can anyone speak to
schedule publishing/update performance on a WAN whose charateristics
is comparable to 45 to 60ms latency?
Any insight would be greatly appreciated!
Ed
implementation. In reviewing the Project Server Configuration 2003
Planning Guide, it states "...an acceptable WAN performance means that
latency should not exceed 30ms."
Based on this statement, we are strongly considering the use of
Windows Terminal Server. However, we're wondering how slow performance
would actually be when opening/publishing schedules over a WAN whose
latency is say between 45 to 60ms.
Understanding we can validate performance speculations using a test
bed (we just don't have the gear right now), can anyone speak to
schedule publishing/update performance on a WAN whose charateristics
is comparable to 45 to 60ms latency?
Any insight would be greatly appreciated!
Ed