►
From YouTube: Overview of performance considerations
Description
Season 1, episode 1 provides a brief overview of SharePoint Online compared to a SharePoint on-Premise farm. It provides a brief overview and starting point around what considerations to make when looking at optimizing performance.
A
A
Today's
agenda
we'll
be
covering
in
cloud
versus
on-prem
and
really
why
that's
important
is
understanding
the
architecture
you
are
coming.
You
potentially
coming
from.
You
may
never
been
an
on-prem
but
understanding
the
differences
and
why
they
are
differences,
and
it's
not
just
a
case
of
hey
you're
headed
on
pram
I
can
just
put
it
in
the
cloud
and
use
it
as
is
already
saw.
It
need
to
start
focusing
on
what
optimizations
actually
available
to
you
in
the
cloud.
A
A
A
Typically,
it's
available
via
VPN,
a
virtual
private
network,
if
you're
not
in
the
office
or
by
a
local
network,
if
you're
in
the
office
and
the
network
distance
is
usually
short,
except
for
users
that
are
remote
in
today's
world,
a
lot
of
users
work
remotely
different
geographies
and
therefore
you
know.
Obviously
this
is
where
cloud
comes
in
strong
into
the
environment.
It
has
higher
latency
for
sure.
Yes,
the
wide
area
network,
but
it's
accessible
from
any
location.
We
are
affected
by
speed
of
light.
A
You
can't
change
speed
of
light
today
and
it
is
variable
for
users
in
different
locations,
and
this
is
one
of
the
reasons
why
some
of
the
optimizations
as
you'll,
see
in
the
different
episodes
as
we
go
through
through
them,
is
why
we
introduce
them.
They
need
to
look
at
font,
size
and
caching
from
a
typical
on-premise
pace.
You'll
see
that
5
to
10
servers
it's
fairly
typical,
some
farms,
obviously
less
some
have
a
lot
more
and
also
you
have
something
called
object:
cash
available,
which
is
in
memory
cash
available
on
the
web
front.
A
End
servers
of
your
farm
I.
Don't
want
you
to
know
what,
though,
about
it.
Those
are
what
it
is.
It's
more
a
case
of
it's
something
that's
not
available,
and
therefore
we
have
to
approach
things
differently
in
the
cloud
in
a
form
of
the
cloud.
We
typically
have
hundreds
of
servers
on
average
object.
Cash
is
not
viable
for
most
and
I,
say
for
most
95%
of
people
or
customers.
Don't
really
hit
those
hundreds
of
servers,
frequently
enough
on
or
off
or
in
memory,
caching
to
make
sense
they
need
to
look
at
high
availability
and
redundancy.
A
If
you
look
at
an
on-prem
space,
it
is
limited
for
most.
Why?
Because
it's
a
cost
factor
7d
are
to
have
high
availability,
is,
is
significantly
higher
cost
and
from
a
maintenance
and
manageability
perspective
or
on-premise.
Where
is
in
cloud,
we
have
multiple
farms
located
in
different
data
centers.
So
at
any
point
in
time
you
have
high
availability
through
the
obviously
the
servers
in
the
farm,
and
you
have
dr
or
redundancy
for
failover
should
anything
occur.
A
Now,
if
we
look
at
what's
coming
up
next
I'll
talk
about
page
Diagnostics
for
SharePoint
and
really
this
is
an
introduction
to
this,
and
maybe
why
I
might
suddenly
jump
into
this.
In
the
end
of
the
day,
the
biggest
things
that
affect
performance
are
around
what
is
on
the
page
and
how
the
page
is
loaded
and
from
a
perspective
of
helping
you
analyze.
This
we
launched
a
song
called
the
page
Diagnostics
for
SharePoint.
It
is
helped
to
analyze
classic
pages
today.
A
Yes,
there
is
a
modern
version
coming
it's
not
available
today,
and
if
you
run
this
on
a
modern
page,
you
will
get
some
insights,
but
it
will
tell
you
this
is
a
modern
page
and
a
tree
isn't
designed
for
that
purpose.
It
runs
rules
and
those
rules
are
really
around
our
recommended
practices
and
why
we
did.
That
is,
we
have
all
these
practices
published
and
those
get
updated
frequently,
but
often
our
found
not
found
by
customers
or
they
are
not
followed
in
use
and
sort
of
taken.
Ok,
there
are
recommendations.
We
shouldn't
really
do
them.
A
If
you
look
under
the
network
trace
tab,
you
will
see
that
if
you
want
to
focus
just
on
rules,
you
use
the
diagnostic
tab
and
it'll
highlight
rules
to
you
and
tell
you
how
you
go
correct
the
following
thing:
these
are
not
not
according
to
recommended
practices.
Yes,
it
doesn't
cover
100%
of
everything.
A
The
idea
is
to
get
you
down
the
most
common
paths
and
the
common
problems,
and
then
you
can
obviously
use
other
tools
which
I'll
show
you
one
of
them
going
forward
now,
while
this
is
not
a
tool
session,
this
is
really
about
introducing
you
to
what
you
should
could
could
do.
What
this
tool
also
does
is
it
provides
additional
support
data.
One
of
those
items
is
the
correlation
ID.
Now,
why
is
the
correlation?
A
Id
important
is
if
we
have
a
correlation,
ID,
a
support
person
now
this
is
not
something
that
on
that
you
can
do
with
the
chip
on
online.
You
could
take
you
do
that
on
print,
but
in
a
shape
an
online
there's,
not
much.
You
can
personally
do
with
the
correlation
ID,
but
you
can
provide
it
to
our
support
teams
and
they
are
able
to
pull
out
different
logs
and
information.
What
we
from
what
we
call
your
less
logs
in
order
to
get
further
diagnostic
information.
A
A
What
you'll
see
is
another
one,
is
the
f12
developer
tools
and
again,
while
this
is
not
a
tool
session,
the
goal
of
this
is
to
show
you
what
page
weight
is
now.
If
you
have
a
look
at
the
image
on
the
right,
what
you'll
see
there
is
it's
showing
what
we
call
the
waterfall,
then
waterfall
is
part
of
the
safety
of
developer
tools
and,
in
fact,
for
project
managers
is
that
you
would
see
that
effect
as
well,
but
in
a
page
it's
a
very
similar,
a
similar
approach.
A
If
you
look
at
that,
you'll
see
that
it's
staggered
a
staggered.
Waterfall
means
that
we
are
waiting
for
each
of
those
actions
to
complete
in
order
to
perform
the
next
action.
This
is
why
we
have
certain
optimization
they're
done
in
the
cloud,
because
they're
heavier
the
page,
the
slower
the
page
will
be.
The
more
items
were
waiting
for
in
queue.
The
so
of
the
page
will
be,
and
these
are
all
factors
then
work
towards,
but
the
page
weight
is
how
heavy
is
the
page.
Is
how
long
this
page
is
going
to
take
to
load?
A
What
else
does
as
f12
developer
tools
gives
you
it's
more
complex
than
the
page
diagnostic
tool?
Pay
diagnostic
tool
is
meant
for
advanced
users.
You
have
12
developer
tools
is
for
advanced
users
to
work
with
their
development
team
or
with
the
administrators.
It
takes
that
one
step
further,
so
you
can
work
out
what
is
actually
going
on
in
this
page.
What
elements
are
causing
the
page
to
load
slowly
and
therefore
impacting
the
weight
of
the
page,
so
it
gives
you
the
waterfall,
as
you
can
see
an
image.
A
It
gives
you
more
deep
detail
details
for
deeper
analysis
right.
So,
while
we're
lumping
this
all
together
and
then
throwing
classic
postmodern
into
the
mix
as
well.
Well,
modern
pages
are
more
performant
than
classic.
Why
are
they
more
performant?
They
were
born
in
the
cloud
that
were
design
for
the
cloud
they
also
use
client-side,
rendering
so
client-side
object
model.
We
therefore
don't
have
to
bring
all
of
that
data
every
time
and
all
the
different
loading
and
elements
every
time
from
the
server
to
load
them
for
every
single
user.
A
If
you
look
at
classic
as
well
its
server-side
rendering
so
what
happens
on
the
server
side,
everything
has
to
go
across
the
line
and
because
it's
higher
latency
we've
got
a
distance
to
travel,
and
you
don't
see
this
as
we
go
on
and
we
talk
about
content,
delivery
networks
and
we'll
talk
about
network
latency
is
and,
as
you
go
on
these
different
episodes,
you
will
go
through
some
of
this.
So
don't
worry!
If
you
don't
get
all
this
now,
then
of
course
you've
got
to
look
at
the
fact
that
classic
is
hard-coded
page
design.
A
What
does
that
mean?
It
means
I,
have
a
master
page
and
I've
bolted.
Then
it'll
be
one
way
if
I,
open
or
mama
our
phone,
it
won't
look.
The
same
it'll
all
be
squished
up
on
this
tiny
little
screen,
whereas
if
I
look
again
at
modern,
it's
what
you
see
is
what
you
get.
It
is
responsive
design.
You
hear
that
key
word
floating
or
responsive
this
responsive
that
responsive
design
is
really
around
adjusting
to
the
page
that
I'm
showing
it
on.
A
In
other
words,
if
I'm
on
my
mobile
phone
and
I
see
it,
it
is
a
much
smaller
screen
and
therefore
it
will
adjust
according
to
that
and
it'll
shift
elements
around
so
that
they
actually
fit
and
make
them
readable
on
the
mobile
device.
We've
also
got
some
accessibility
elements
in
Martin.
If
you
have
images
you
are
able
to
set
taglines,
intend
and
prompted
text
to
enable
you
know
so
that
we
can
then
cater
for
different
different
levels
and
different
people
in
different
ways.
They
need
to
work
and
different
understandings.
A
All
this
is
around
making
making
ship
or
more
accessible
to
everyone,
and
a
lot
of
that
is
customizable
as
well.
It's
also
editor
and
author
focus
so
an
editor
and
author.
It
makes
it
far
more
seamless
for
them
to
work,
obviously
design
for
the
mobile
as
well
and,
as
I
said,
Iranian
uses
clients
on
rendering.
Now
these
are
just
a
couple
of
points
taken
down,
but
I'm,
just
going
through
the
minute
I'll
see
as
we
go
through
these
episodes.
You
will
learn
about
all
these
elements
and
why
they're
so
important,
then
to
end
it
all.
A
We
have
helpful
links
and
these
links
as
you'll
see,
will
appear
again
and
again
these
different
seasons
and
episodes.
Please
follow
us
along
you'll,
see
where
we're
part
of
the
PHP
channel
and
feel
free
to
post
comments.
Let
us
know
what
other
things
you'd
like
us
to
talk
about.
Thank
you
for
your
time
today.