Escolar Documentos
Profissional Documentos
Cultura Documentos
The New York site has some basic network requirements that are required to make sure that the fourstorey building and its 430 users are capable of functioning and have access with the applications to do
their job. Also making sure the applications are accessible via the Toronto HQ site and internet.
With the applications needed there are factors we need to take into consideration for the network: the
amount of traffic, bandwidth and latency are among some.
IP Telephony system
The first application is the IP telephony system hosted in the HQ. In order to keep your conversations
clear and free of disruptions, we need a certain amount of bandwidth. As long as we have a good
upload/download stream, we should be able to use the application correctly. The more accurate results
using this application will come from using a fixed connection to the internet and not WIFI.
Here are guideline network requirements to use the IP Telephony system:
Full Quality Audio (G711 Codec)\- Uses 87 kbps for each concurrent phone call (NEB)
Compressed Audio (G729 Codec)\- Uses 33 kbps for each concurrent phone call (NEB)
So the calculation for a typical DSL connection would be:
DSL connection:600 kbps upload / 5000 kbps download
Gives us (Full Quality):600 kbps / 87 kbps = 6 concurrent calls
Gives us (Compressed Quality):600 kbps / 33 kbps = 18 concurrent calls
We use the upload bandwidth in the calculation, this will limiting factor for voice-over-IP.
As for the 430 users and the usage of 20% of concurrent users will 86 at the same time.
The required bandwidth for voice-over-IP is 16 Mb/s
V
e
r
y
AM
cL
eH
h
tiidee
v giaa
ithuvv
y tm
yy
M5123
e 000
s
s
a
g
e
s
s
e
n
t
p
e
r
d
a
y
M2481
e 0002
s 0
s
a
g
e
s
r
e
c
e
i
v
e
d
p
e
r
d
a
y
A5555
v 0000
e
r
K
K
K
K
a
B
BB
B
g
e
m
e
s
s
a
g
e
si
z
e
M2481
e 0002
s 0
s
a
g
e
s
r
e
a
d
p
e
r
d
a
y
M1246
e 0000
s
s
a
g
e
s
d
e
l
e
t
e
d
p
e
r
d
a
y
O2222
W
A
l
o
g
o
n
a
n
d
l
o
g
o
ff
p
e
r
d
a
y
E
V
M
e
a
r
i
y
l
CM
l LeHH
i i dee
egi aa
nhuvv
t t myy
O1257
f, , , ,
f 3628
i 0000
c0000
e
O
KKKK
u
BBBB
t
////
l
dddd
o
aaaa
o
yyyy
k
////
uuuu
2ss s s
0eeee
0r r r r
7
O6123
W, 246
A1, , ,
9223
0273
000
K
BKKK
/ BBB
d/ / /
addd
yaaa
/ yyy
u/ / /
suuu
es s s
r eee
rrr
If we apply 430 using the heavy column Office Outlook users we would calculate the average
network traffic during an 8 hour day.
Example: If your company has 430 heavy Office Outlook 2007 users, heres how to calculate
the average network traffic, measured in bytes per second. Network bytes/sec = (430 heavy
users (5,200 KB/user day)) (8 hr/day 3600 sec/hr) = 79.6 KB/secAssuming a daily peak
of twice the average usage, your network connection would need to support approximately
159.2 KB/sec.
Sharepoint online we have calculation for an average interaction transfer approximately 100kb.
The typical user generates 36 interactions per hour. About 10% of the company users will be
active at the same time.
Example: If your company has 430 SharePoint Online users, heres how to calculate the
average network traffic for each user, measured in bytes per second. Network bits per second =
(100,000 bytes/load 8 bits/byte 36 loads/hr) 3600 seconds/hr = 8000 bits per secondA
company with 430 users would have approximately 100 active users at any one time. Those 430
users would require approximately 430 x 8000 bits per second or 800 kilobits per second of
available network bandwidth. Assuming a daily peak of twice the average usage, your network
connection would need to provide approximately 1.6 megabits per second of network
bandwidth.
NCCD
ue e i
m
n ns
bt t t
er r r
ra a i
l lb
o wu
f it
te
u hd
s
e r
r e
s g
i
o
n
a
l
s
i
t
e
s
1B BB
0a a a
0n n n
-d d d
5www
,i i i
0d d d
0t t t
0h h h
r rr
a aa
n nn
g gg
e ee
s ss
o oo
f ff
3 11
m. .
e 55
g MM
a bb
b pp
it s s
s ((
p TT
e 11
r ))
s aa
e nn
c dd
o gg
nrr
d ee
( aa
Mt t
b ee
prr
s)ww
( i it
dth
u hl
all a
Tat
1te
) en
a nc
n ci
die
g es
r sn
e no
ato g
e gr
r re
we a
it a t
hte
lae r
ter t
nth
cih a
e an
s n1
n 10
o 00
g 0m
r ms
es
at
e
r
t
h
a
n
1
0
0
m
il
li
s
e
c
o
n
d
s
(
m
s)
1B BB
0a a a
,n n n
0d d d
0www
0i i i
d dd
t tt
h hh
r rr
a aa
n nn
g gg
e ee
s ss
o oo
f ff
3 11
M. .
b 55
p MM
s bb
( pp
d ss
u((
alTT
T 11
1))
) aa
a nn
n dd
d gg
grr
r ee
e aa
att t
e ee
r rr
www
it i it
hth
lah l
tel a
n at
cit e
e en
s nc
n ci
i
e
e
s
s
o n
n
g o
o
r g
g
e r
r
at e
e
e a
a
r t
t
t e
e
h r
r
a t
t
n h
h
2 a
a
5 n
n
0 5
5
m 0
0
s 0
0
m
m
s
s
1B BB
0a a a
0n n n
,d d d
0www
0i i i
0d d d
t tt
h hh
r rr
a aa
n nn
g gg
e ee
s ss
o oo
f ff
3 11
M. .
b 55
p MM
s bb
( pp
d ss
u((
alTT
T 11
1))
a
a
n
n
d
) d
g
a g
r
n r
e
d e
a
g a
t
r t
e
e e
r
at r
w
e w
i
r it
t
w h
h
it l
l
h a
a
la t
t
te e
e
n n
n
ci c
c
e i
i
s e
e
n s
s
o n
n
g o
o
r g
g
e r
r
at e
e
e a
a
r t
t
t e
e
h r
r
a t
t
n h
h
2 a
a
5 n
n
0 5
5
m 0
0
s 0
0
m
m
s
s
Office live meeting offers 2 different clients: office live meeting client(window-based) and
office live meeting Web access (web based). The bandwidth of these values are going to be
calculated in Kbps for one person.
B
a
n
d
w
i
d
t
h
Fr
ue
nq
cu
ti
ir
oe
nd
D5
a6
tK
aB
p
s
t
r
a
n
s
f
e
r
V8
o0
iK
cB
ep
s
(
5
0
K
B
p
s
m
i
n
i
m
u
m
)
V3
i5
d0
eK
oB
p
s
(
5
0
K
B
p
s
m
i
n
i
m
u
m
)
O7
f0
f0
iK
cB
ep
s
(
R
1
o
0
u
0
n
K
d
B
T
p
a
s
b
m
l
i
e
n
i
m
u
m
)
The bandwidth requirements are cumulative for each function here, if you want to use voice,
video, and Office RoundTable, the minimum bandwidth would be 50 + 50 + 100 = 200 KBps
per user. The minimum bandwidth recommendation for the MWA client is 56 Kbps.
This amount will be 256 Kbps.
Salesforces :
You can then calculate bandwidth as follows:
Bandwidth = Avg. Page Size(in kilobits) * Number of Users / (Seconds between page views +
Page load time)
***Remember bandwidth is calculate in BITS not BYTES. If a compressed Salesforce page has
a size of 15 kilobytes, that's 120 kilobits of bandwidth.
As an example, let's say Page Size = 120kilobits Users = 430, Seconds between page views =
120 (2 minutes) and page load time = 2 seconds
120 * 430 / (120 + 2) = 422.95 kbps of bandwidth.
Of course, if all 10 people open a new page at the same time, it will be much slower. If only 1
person opens a new page while the other 9 are doing something else, it should be much faster.
Minimum requirements:
Upstream: 1 mbps
Downstream: 1 mbps
Latency: 200ms or better
ASABBB
ucua a a
dednn n
ini dd d
oaowww
ri i i
cipdd d
ooat t t
dyhh h
el a a
c oa u u
aud d
ddi i
i oo
pp
bo a a
p
i yy
ta l l
ry o o
al a a
to d d
ea , ,
d
II
( PP
Ka h h
Bne e
Pda a
S dd
)I e e
Pr,r,
UU
D
P
,
R
T
P
,
S
R
T
P
D
a
P
h n
,
e d
R
a f
T
d o
P
e r
a
r w
n
o a
d
n r
S
l d
R
y e
T
( r
P
Kr
(
b o
K
p r
b
s c
p
) o
s
r
)
r
e
c
ti
o
n
(
K
b
p
s)
GP11 1 2
.e24 5 2
7e84 9 3
2r. . . .
2-00 6 6
t
So
tep
re
ee
or
C
o
n
f
e
r
e
n
c
i
n
g
*We selected a high payload for this scenario and the codec G.722
MM
a in
Rxi i
e mm
suu
o mm
l vi vi
Vu d d
i ti e e
do o o
en p p
oa a a
n yl yl
do o
ca a a
os d d
dp bi bi
ee t t
cc r r
t at at
re e
a( (
ti K K
ob b
pp
s) s)
1
H
2
.
8
2
0
6
x
4
72
/
7
25
R 0
00
T 0
(0
V
1
i
6
d
:
e
9
o
)
*we selected a high payload for this scenario and codec H.264/ RTVideo
RTCP Bandwidth
Me R
dia T
C
P
m
ax
i
m
u
m
ba
n
d
wi
dt
h
(
K
b
ps
)
Au
5
dio
Vi
de
o
(O
nly
H.
26
4
or
RT
10
Vi
de
o
bei
ng
sen
t/re
cei
ve
d)
Vi
de
o
(H.
26
4
an
d
RT
Vi 15
de
o
bei
ng
sen
t/re
cei
ve
d)
SPSS
it is hard to give an accurate need but we can give a general approximation for this building and
users.
BANDWIDTH
Minimum bandwidth (between client PC and web server) of approximately 256 kbps for
'standard' users
For 'super-users' (those running more complex tasks), recommended bandwidth of approx
512kbps or more
NETWORK LATENCY
Relatively low network round-trip latency (for example less than 80ms 'round-trip' or so)
NOTE:
The above bandwidths are the required/recommended-minimum values per active user.
Therefore, if you have 20 remote 'standard' users who are actively simultaneously using the
system, then this will require a central ('hub') dedicated (Controller-only) network pipe of
approximately 5Mbps (or more) at your central 'server' location.
Again, performance is a subjective quantity - different customers will have different
needs/expectations. However, as a rough/approximate guideline, the author suggests:
Bandwidth for Citrix:
Higher bandwidths will make certain tasks (especially printing and file import/export &
Ideal: less than 150ms - users should experience good Citrix performance
OK/poor: latency between 150ms and 300ms users will find the Citrix application usable,
In addition, you may find it useful to enable Citrix functionality (such as "SpeedScreen
Bad: Latency > 300 ms the end-users will find the Citrix application will perform badly.
It may be so poor that it is unusable, especially if the latency is above approx 450ms.
You must enable Citrix functionality (such as "SpeedScreen Latency Reduction") to try to