You will need information like: bytes per transaction type number of transaction types per user number of users performing transaction type(s) how many transaction type(s) performed per minute or per hour available link capacity at source & destination Another way of saying this: transaction type X consumes Y kilobits/sec for Z seconds. There will be R number of these types of transactions per min/hr/day. There are J number of users performing these transactions Remember that transactions across a WAN will be affected by: Link congestion latency or delay packet loss link availability Latency or delay can be caused by: distance between client and server serialization of putting the packets on the line device queueing forwarding delays protocol type(s) Of course, application performance is also affected by client and server resources (memory, disk, processor).

You will need information like: bytes per transaction type number of transaction types per user number of users performing transaction type(s) how many transaction type(s) performed per minute or per hour available link capacity at source & destination Another way of saying this: transaction type X consumes Y kilobits/sec for Z seconds. There will be R number of these types of transactions per min/hr/day. There are J number of users performing these transactions Remember that transactions across a WAN will be affected by: Link congestion latency or delay packet loss link availability Latency or delay can be caused by: distance between client and server serialization of putting the packets on the line device queueing forwarding delays protocol type(s) Of course, application performance is also affected by client and server resources (memory, disk, processor).