►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
C
A
A
C
A
C
First
there's
a
someone
who
sells
wood
carvings
effectively
of
all
the
different
tracks
and
then
friends
suggested.
Oh
no
wait
like
there
might
be
a
3d
printed
thing
on
Thingiverse,
and
so
they
found
it,
and
so
this
biz
may
see
every
Formula
one
track
from
the
2018
season
available
as
a
Thingiverse,
3d
print
and
then
of
course,
Scott
being
the
person
I
know
who
does
very.
C
Explaining
what
it
is,
I
got,
Scott
being
the
person
I
I
know
who
does
3d
printing
I,
send
it
to
him.
I
said:
oh,
can
you
just
do
this
he's
like
yeah
no
problem
and
didn't
really
quite
realize,
I
think
how
many
there
were
here
exactly
right.
Each
one
of
these
is
like
eight
by
eight
inches
and
then
you
kind
of
math
on
the
wall
like
that
and
then
look
you
know
cool
if
you're
into
that
stuff.
So
we
might
try
some
samples
and
then
we'll
see
if
I
can't
the
other.
C
A
What
you
could
do
would
be
a
a
Plexiglas
sheet,
LEDs
on
the
side
going
laterally
to
light
up
the
the
whole.
B
A
B
A
C
A
They're
not
like
yeah,
okay,
okay,
so
what
I
got
to
do
then?
Is
I
got
to
go
like
this
and
I
got
to
go
all
right:
yeah
90
degrees
on
the
X
yeah,
okay,
that
means
to
fit
in
the
bed
yeah.
It
doesn't
fit.
Okay,
so
negative,
33
on
the
Z
yeah,
hey
yeah,
all
right,
then
I
have
to
go
and
do
what's
called
slicing
yep.
So
then
we
figured
this
out
here.
Okay
that'll
probably
fit
yeah.
A
Then
it
says
all
right:
it'll
cost
a
dollar
it'll
weigh
20
grams,
it's
six,
six,
sixty
swell
Satan's
number
of
millimeters
and
take
an
hour
and
a
fifteen
minutes,
and
that
hour
15
minutes
is
really
about
45.
So
that's
going
right
now,
so
I'll
do
that
for
each
one
Wow
and
then
you
know
like
for
some
of
them.
I
don't
know
like
I've
only
done
two
so
I'm.
Definitely
whatever
sliced
yeah,
yeah,
so
they're
all
wrong.
So
here's
a
funny
shape
one
right
by
the
way
it
all
looks.
The
thing
is
from
my
perspective,
as.
B
A
B
A
A
A
A
C
A
B
A
B
A
C
C
C
A
B
A
A
jeff
fretts
did
a
live
8
hours,
hyphenated
workshop
for
those
of
you
who
love
live
content
and
cannot
get
enough
of
it.
Take
a
look
at
live
or
jeffrey
live
jeffrey,
Fritz
comm
he
had
Glenn
on
and
it
was
basically
live
coding.
So
if
you
think
that
this
show
sucks
take
a
look
at
this,
it's
actually
pretty
cool
and
he's
got
a
playlist
up
here,
which
was
pretty
cool
and
I
believe
he
did
a
specific
one.
Jeff
Fritz
and
friends
see
all
this
good
stuff
and
where's
the
one
he
did.
A
B
A
This
here
is
really
cool
and
he
actually
had
sheriff
or
any
of
Maria
and
I
was
last
and
in
in
my
thing
you
might
I.
Think
I
told
you
about
this.
They
tell
you
that
I
installed
PowerShell
on
a
power
shell
core
on
a
Raspberry
Pi
along
with
dotnet
core
and
I,
took
my
podcast
website,
which
is
written
in
asp.net
core
2.1
right
and
got
it
running
fairly
nicely
on
a
Raspberry
Pi
very
effectively
on
a
Raspberry
Pi.
It
required
I,
don't
know
two
hours
to
set
up.
C
C
C
So
if
you
I,
don't
know
if
you
remember,
but
when
the
200
came
out,
I
did
record
a
bunch
of
live
streams
where
I
updated
it
from
1
1
to
200,
but
I
never
deployed
it.
I
even
changed
it
to
razor
pages
did
a
whole
bunch
of
stuff.
It
never
got
deployed
because
the
GDP
cookie
stop
happened
at
the
same
time
and
I
couldn't
do
both.
C
C
Talking
talking
talking,
yes,
yes,
I
did
want
to
talk
about
some
stuff.
Today,
I
was
hoping
that
we
could
do
a
recap
of
what
happened
to
build
because
I
don't
think
we've
met
since
build
happened
and
we
had
an
a/c
come
out
for
2.1.
We
I
can
talk
about
what
the
plans
are
for
2.1
RTM,
which
is
very
close,
like
really
really
really
close
fact.
I
think
the
last
time
I
was
on
the
show.
C
B
A
C
C
C
A
C
C
So
now
what
we
have
in
vs
is
the
self-contained
publish,
is
an
option
during
publish
to
as
your
app
service
in
vs
now,
which
makes
it
super
easy
to
deploy
whatever
version
you
are
using
on
your
build
machine
because
you
just
self-contained
it
with
your
app
and
because
of
all
the
build
improvements
and
startup
improvements,
we've
done
that
actually
performs
pretty
well
so
I
see.
One
will
be
the
last
preview
that
we
ever
deployed
to
web
service.
It
is
on
there,
but
we
don't
plan
on
doing
another
one.
C
C
Oh,
that's
cool
yep
and
what
I
hope
to
do
is
tomorrow
I'm,
going
to
put
together
a
wiki
page
on
a
spinet,
slash
home
which
points
people
to
where
they
can
download
the
RTM
sdk
a
week
early,
if
they're
so
inclined
to
give
us,
you
know
to
basically
get
some
early
feedback,
so
the
reality
is
the
build
that
we
have
right
now
is
almost
guaranteed
to
be
the
build
that
we
ship
next
week.
I
cannot
foresee
anything
that
we
would
find.
C
A
C
Lots
of
reasons
why
we
have
to
be
date
driven
by
certain
dates:
okay
and
some
of
them-
are
due
to
partner
teams
who
are
relying
on
an
RTM
date
to
coincide
with
their
products,
our
TM
date.
Some
of
them
are
to
do
with
processes
around
how
servicing
works.
Some
of
them
are
to
do
with
partners
that
embed
dotnet
core
in
their
their
products
that
aren't
Microsoft
base.
There's
a
whole
bunch
of
reasons
why
we
can't
just
say
it's
ready.
You
were
shipping
it
okay,
so.
A
C
More
than
that,
what
we're
hoping,
it'll
probably
be
two
weeks,
so
what
we're
hoping
is
you
know,
ITM
will
go
out
next.
Wednesday
like
publicly
like
I,
said
we'll
do
a
soft
launch
tomorrow
and
folks
who
want
to
could
go
and
grab.
It
won't
be
on
NuGet.
Tomorrow,
though,
so
you'd
have
to
configure
them,
I
get
feet,
you
get
packages
yeah,
it's
not
worth
it
right,
so
I
mean
like.
C
So
we'll
do
in
that
first
release,
but
none
of
them
should
be
game
like
none
of
them
should
be.
It
should
be
things
that
would
prevent
someone
from
running
most
of
them
have
workarounds
or
they're.
You
know
they're
either
things
that
would
just
need
to
fix
in
order
to
be
correct
or
more
stable,
whatever
it
is
so
yeah.
So
then
II
way,
that's
the
timeline
for
the
2.1
stuff,
like
I
said,
hopefully,
tomorrow
I'll
share
for
those
folks
who
are
inclined
and
want
to
get
stuff
super
early.
C
A
A
A
C
A
A
C
A
C
C
C
C
When
a
ocean
gets
removed
from
a
machine
for
framework
dependent
apps,
you
will
never
get
rolled
forward
from
an
ass
like
basically,
a
preview
of
any
sort
to
an
RTM
build,
and
so
installing
RTM
builds
on
a
machine
can
cause
issues
when
it
comes
to
cleaning
them
up
later.
So
we
would
rather,
because
I
basically
you
remove
them
all
the
apps
that
we're
running
on
them
break.
C
So,
due
to
size
constraints
and
a
whole
bunch
of
things
we
from
now
on
will
likely
not
release
those
on
as
your
app
service
and
if
you
deploy
an
internet
core
app,
that's
using
one
of
those
builds
you'll
just
have
to
do
a
self-contained
deployment
or
user
container
using
app
service
for
containers
or
use
the
extension
that
you
alluded
to
which
actually
brings
the
runtime
under
the
under
the
machine
for
you.
So.
C
Other
options,
but
so
that
shouldn't
be
an
issue,
the
other
one
was
the
VCS,
so
some
folks
who
are
using
VST,
s4c,
I
and
CD
we're
currently
syncing
with
them
on
the
timing
for
that,
so
how
quickly
we
can
get
the
2.1
bits
available
for
build
agents
for
VST
s
and
we'll
circle
back
shortly
to
let
you
know
you
know
when
that
will
when
that
will
happen.
Obviously,
when
we
do
the
post
to
announce
that
one
is
public
and
rtems
will
include
details
of
those
things,
if
there's
any
lag,
I
had.
A
A
A
B
C
B
C
A
C
A
C
C
C
A
C
C
A
C
Is
fairly
straight
to
make
it
idiomatic?
If
you
want
to
use
some
of
the
new
features,
then
that's
just
an
extra
step
and
it's
not
a
huge
amount
of
work
either
yeah
yeah
and
then,
in
terms
of
when
we
do
mark
to
one
say
it's
two
one:
three,
it
comes
out
yes
in
August,
then
the
clock
starts
ticking
on
the
previous
LTS
release.
C
A
C
A
C
A
C
Lts
basically
means
two
things
once
we
once
we
mark
a
release
as
LTS
there's,
two
there's
two
things
that
we
want
to
make
sure
of
when
we
do
that.
One
is
that
we
have
some
confidence
in
its
stability,
so
it
isn't
just
the
brand
new
release
we
throw
over
the
wall,
which
is
why
two
one,
oh
won't
be
LTS
will
do
a
couple
of
servicing
rounds
on
it
first,
because
customers
expect
that
whatever
is
marked
as
LT
s
is
ready
to
use
with
somewhat
low
churn,
if
that
makes
sense
right
and
high
high
confidence.
C
The
second
thing
is
you
get
long-term
support,
so
you'll
get
support
on
that
train,
not
on
that
exact
version,
but
on
that
train,
you'll
get
support
for
three
years
or
two
until
twelve
months
after
the
next
LTS
comes
out
so
and,
as
you
pointed
out,
the
first
one
has
been
about
three
years.
So
two
one.
Once
you
go
to
two
one
three,
so
that's
the
next
LTS
you
will
be
to
get
support
on
the
LTS
train,
you're
expected
to
keep
up
to
date.
C
So
if
it's
a
two
and
four
and
then
a
two
one,
five
and
then
you
find
a
bug
and
you
didn't
update
two
two
one:
five,
you
can
log
a
microsoft
support
ticket.
You
know
through
paid
support
and
say
hey
I'm
using
LC.
Yes,
I
found
this
issue.
Can
you
help
help
me
out
and
if
we
go
yeah
we
already
fixed
that
it's
in
two
one,
five
you're
expected
to
update.
Obviously
not
gonna
go
back
and
patch
two
one,
three
with
some
magic
patch.
You
have
to
go
forward
to
two
one
five.
C
Similarly,
if
we've
already
shipped,
if
you're,
not
using
LTS
and
you're,
not
using
Microsoft
paid
support,
if
you're
on
the
current
train,
so
you're
just
relying
on
github
and
not
paying
Microsoft
for
support,
you
have
to
stay
on
the
current
release,
and
so
that
means
you
find
a
bug
in
two
one
and
it
doesn't
meet
our
servicing
bar.
Then
we'll
say
yep
we'll
fix
that
it's
going
to
be
in
2.2.
It's
basically
how
that
works
and
2.2
we're
currently
slated
to
come
out
in
around
November
this
year.
We
hope
so
yeah.
So
that's
basically
there's.
C
This
is
effectively
to
trains.
People
who
are
using
LTS
are
the
ones
who
typically
are
used
to
calling
microsoft
support
and
paying
for
support
when
they
find
an
issue.
That's
that's
that
that's
how
you
need
to
think
about
that
current
is
for
everyone
else
where
you
just
generally,
when
you
have
an
issue
you
can
log.
A
github
issue
will
investigate
it,
based
on
sort
of
the
open
source,
support
model
and
you'll
generally
get
a
fix
as
part
of
the
next
release.
C
That's
that's
kind
of
the
two
options
that
you
have
if
you're
in
Visual
Studio
and
you
only
get
dotnet
core
through
Visual
Studio
just
use
the
version
that
comes
with
Visual
Studio.
So
today,
200x
is
what's
in
Visual
Studio
and
it
gets
updated
every
time.
This
is
updated.
Your
things
done.
That
will
change.
So
we
will
update
to
ode
2.1
in
Visual
Studio.
In
probably
the
next
release
the
next
minor
release
of
Visual
Studio.
C
So
what
15.8
so
far,
you
will
change
the
2.1
in
vs
and
15.8
if
everything
goes
according
to
plan
which
of
course,
lines
up
with
the
support
stuff.
We
just
talked
about
whoa.
Look
at
this
segue
back
to
how
we
opened
the
show.
Oh
now,
so,
unfortunately,
I
don't
know
the
tracks
all
of
them.
Well
enough,
my
son.
C
C
B
C
That's
your
really
cool
track,
so
part
of
that
track,
which
you
can't
see
on
here,
I
think
it's
the
top
bit
the
top
bit
right
up
the
top
day
are
the
buck
at
the
top
of
the
screen.
That
part
of
the
track
is
inside
an
old
baseball
stadium.
Is
it,
and
so
you
can
sit
in
there
and
you
can
see
the
cars
come
in
and
come
around
right
in
front
of
you
in
stadium
seating.
It's
actually
super
super
cool
cool.
A
C
A
C
C
A
C
A
C
C
A
You
know
blah
blah
blah,
don't
don't
make
decisions,
it's
all
lies
yeah.
This
is
a
draft
right,
yep,
no
I'm,
looking
up
here
and
I
see
asp
net
core
yeah,
nearly
7
million,
now
I'm
noticing
I'm
imagining
this
kind
of
logarithmic
graph
approaching
7
point
1
million,
but
never
reach
it.
Yes,
we
had
some
theoretical
speed
of
light.
Yeah.
A
A
C
A
B
A
C
Percentage
there,
which
basically
says
you
know,
number
two
wait.
We
are
number
nine
or
ten
here
at
the
moment,
and
we
are
ninety
nine
point,
three
of
the
of
the
two
top
ones
which
are
basically
in
the
same
number
that
will
not
be
99
anymore.
We
before
we
fully
expect
them
to
pull
away
like
I,
can
see
the
top
ones
are
written
in
native.
A
C
A
C
C
A
C
A
C
C
A
C
Different
about
this
round,
it's
a
couple
things
one.
This
is
the
first
round
on
the
new
hardware
that
Microsoft
sponsored,
so
we
actually
provided
these.
They
announced
this
in
the
last
actually
was
the
last
round.
Maybe
anyway
we
we
have.
We,
we
better
loan,
this
Hardware
to
take,
compare
it
at
their
offices
and
the
eastern
way
and
they're
just
commodity.
Dell
servers
like
anyone
could
go
and
buy
these
service
I'm
sure.
C
C
The
car
in
some
ways,
less
I,
bet
a
similar
CPUs.
They
might
even
have
more
CPU.
They
definitely
a
more
ram.
So
they're
they're
not
like
holy
crap
servers,
they're
they're,
good
service.
You
know
they're,
not
they're,
not
the
best
over
the
world.
So
and
this
was
ten
gig
network.
As
I
said,
Nick
asked.
If
we're
going
to
update
the
network.
What
are
we
going
to
so
we're
going
to
a
hundred
gig
network,
we're
going
to
fibre
qfs
joining.
C
C
C
A
C
A
C
A
C
A
A
C
Know
so
they're
clustering
at
the
top
as
well
they're
they're
hitting
a
limit,
and
we
think
that's
the
packet
switching
limit
Oh,
because
that
used
to
be
a
lot
more
spread
out
when
we
didn't
have
as
much
CPU
to
use.
Now,
we
have
a
lot
more
CPU.
We
see
that
we're
getting
limited
here,
so
we're
hoping
that
the
move
to
the
fiber
network
will
also
potentially
increase
our
messages
per
second,
because
this.
C
C
C
A
C
A
A
C
C
Platform,
so
you
know
how
the
asp
net
core
platform
tests
aren't
using
middleware
they're
kestrel
direct,
so
you
can
go
look
at
the
source
code.
Actually,
this
is
a
really
you've
seen
this
code
open
a
new
tab
and
go
to
github.com
slash
a
spinet,
slash,
kestrel,
HTTP
server,
kestrel
HTTP
server
al.
How
do
we
do
this
HTTP
server?
I
know
it's
one
word
kestrel
HT
to
be
served.
I'm.
B
B
C
A
C
C
C
A
C
A
C
C
A
A
A
C
C
Know
you
didn't
mean
that,
but
people
say
those
things
is
in
the
micro
service
as
well.
When
people
use
things
like
go,
we
have
seen
real-world
examples
where
people
do
this,
so
they
go,
gives
you
an
HTTP
server
and
not
much
else
out
of
the
box.
Otherwise
you
pull
all
the
stuff
in
and
they
go
I
want
my
entire
service
to
be
500
lines
of
code.
It's
a
self-contained
app.
This
is
what
I
want
it
to
look
like,
and
this
is
what
they
end
up.
Looking.
C
C
C
Is
this
is
bait
like
I
said
this
is
basically
it
avoids
the
whole
middleware
pipeline
in
an
HTTP
context
and
all
that
stuff,
I'm
VI
overhead
and
all
that
stuff.
It's
literally
just
kestrel
request
comes
in
you,
get
a
request
and
then
on
process
request.
Async
online
54,
which
is
after
the
start
line,
gets
read.
You
then
go
well.
Am
I
doing
Jason
on
doing
plain
text
you
can
navigate
to.
C
Switches
and
then
you
get
down
to
business
and
then
pipe
writer
well
I
know
that's
part
of
the
pipelines
that
call
2.1,
which
again
came
out
of
all
the
work
on
Kestrel.
Now
what
Nick
Craver
just
made
a
very
interesting
comment
in
the
thing
he
says,
this
is
how
they
write
the
code
and
a
lot
of
Stack
Overflow
as
well
with.
A
Hospice
because
to
be
cleared
and
Nick
can
correct
me
if
I'm
wrong,
we
should
have
him
on
as
a
guest
me
can
show
us
the
code.
That's
because
Stack
Overflow
feels
that
performance
is
a
feature
and
they
are
obsessive
about
performance.
But
most
of
us
who
are
working
on
you
know
at
Aflac
or
Little
Debbie,
snack,
cakes,
doing
text
boxes
over
data
are
not
that
obsessive
about
perf.
So.
C
It's
interesting
traditionally
that
might
be
true
with
dotnet,
but
the
reality
is
and
in
the
landscape
of
things
like
Java
people
have
been
obsessed
about
these
things
for
a
lot
longer
than
us,
and
so
there
you
see
this
type
of
API
and
server
writing
a
lot
more
frequently,
really
yeah
and
so
yeah.
That's
what
Nettie
is
and
yeah
I.
A
Feel
like
it
depends
like
I'm
what
you're
trying
to
accomplish
like
when
I
was
doing
the
banking
stuff
back
in
the
day,
if
I
was
gonna,
do
like
check
imaging
and
stuff
yeah
I
would
optimize
the
heck
out
of
it
cuz.
It
was
truly
a
micro
service.
It
was
15
years
ago,
but
is
a
micro
service
and
it
was
clearly
a
problem,
but
like
optimizing,
the
heck
out
of
just
doing
pages
and
doing
regular
business
right.
C
A
C
Might
have
an
extremely
a
high
like
I
know,
stack
overflows,
WebSocket
server.
For
example,
they
wrote
that
as
custom
is
highly
optimized
for
this
reason,
because
they
want
to
have
a
server
that
does
a
very
specific
thing
without
any
overhead
and
yeah
Nick
and
Mark
have
talked
about
that
before
and
I
believe
he's
rewriting
it
on
pipelines
to
help
that
so
there's
an
interesting
example
of
something
that's
new
in
this
round
and
now
I'm.
Looking
at
myself,
because
you're
sharing
my
still
sharing
yeah.
C
C
Just
as
fast
I'm
still
seeing
your
screen,
but
yeah
I'm
not
presenting
everyone,
no
so
yeah,
as
I
said,
that
was
just
one
of
the
new
things
in
this
tech
empower
round
is
that
they
we
have
submitted
this
platform
level
test
the
thing
that
it
means
as
Tekken
Power
has
a
visualization
that
you
can
bring
up.
That
shows
you
the
overhead
of
the
framework
for
the
platform
that
you're
using
and
so
then
you
can
actually
say
well
yeah
like
if
I
do,
raucous
July
get
100%
and
I
add
middle
where
I
drop
X
percent.
A
C
A
C
A
B
A
C
C
C
C
Yes,
that
libby
v
was
a
sea
library
that
abstracts
the
socket
API
is
between
Linux
Mac
and
Windows,
and
we
were
using
that
before
it
was,
is
a.
It
was
the
easiest
path
to
go
across
plat
we
have
since
rewritten
the
dotnet,
sockets
stack
fallen
and
for
windows,
improved
it
for
Windows,
and
so
we
don't
need
that
shim
anymore.
We
can
just
talk
directly
to
system
net
sockets
and
let
it
do
what
it
does
on
every
platform.
And
it's
now
good
enough
that
we
can
do
that
and
that's
one.
C
C
A
A
C
C
A
A
A
A
A
A
Up
to
that,
but
it
all
adds
up,
though
this
all.
C
C
C
A
Why
is
this
being
brought
up
in
20,
so
this
is
one
of
those
things
correct
me
if
I'm
wrong,
I
always
think
it's
funny
when,
when
I
see
I'm,
not
gonna
name
names,
but
you
know
the
various
windows,
bloggers
and
people
about,
like
you
know,
oh,
my
goodness,
we
just
Microsoft
is
doing
X,
Y,
Z
and
then
I'm
thinking
to
myself.
You
know
if
you
watch
the
github
repos
we
talked
about
this
two
years
ago,
yeah.
C
A
C
Promise
as
to
when
they'll
be
productized
yeah,
so
and-
and
this
is
one
of
those
cases
where
the
team
actually
didn't
have
your
overall
team,
like
at
my
level
and
above
we
didn't,
have
a
plan
for
this
to
become
part
of
the
product
into
one.
It
just
kind
of
happened,
which
is
great
so
tier
JIT
is
we
have
you
know
everyone
understands
what
JIT
is.
C
A
C
Apple
juice,
nice,
so
we
have
a
bunch
of
techniques
for
optimizing
that
process
in
the
balance
between
how
fast
your
application
starts
versus
how
fast
it
runs
once
it's
been
kitted
and
turned
into
machine
code
right,
so
we
call
that
startup
performance
versus
steady-state
performance.
You
would
have
heard
of
engine,
which
was
what
we
had
in
the
past,
which
enable
you
to
a
pre
JIT,
the
application
or
what
we
call
a
ot,
compile
ahead
of
time,
compile
the
application,
so
that
was
in
machine
code
in
the
assembly
on
disk
and
the
runtime.
C
C
Multiple,
so
we
have
a
new
thing,
which
is
a
cross-gen
is
basically
engine
for
cross-platform.
We
use
cross-gen
to
pre-compile
a
spinner
core
and
dotnet
core
to
make
the
star
the
application,
as
fast
as
it
can
be.
Unfortunately,
cross-gen
has
some
limitations
which,
in
order
to
maintain
like
serviceability
of
the
Assemblies
of
the
questions
and
a
bunch
of
other
things,
it
is
slower,
as
in
it's
faster
to
startup,
but
the
steady
state
performance,
the
actual
quality
of
the
code,
isn't
as
good.
It
can't
as
aggressively
optimize
the
code.
A
C
A
A
A
A
C
To
finish
the
process
of
what
happens,
you'll
start
the
app
things
that
the
cross-gender
will
load
very
quickly.
Tiered
compilation
will
kick
in
to
do
a
cheap
compilation
of
the
stuff
that
needs
to
be
jittered
to
get
the
rest
of
the
app
running,
and
then
it
can
kick
off
a
higher-quality
background
compilation,
including
the
stuff
that
was
originally
loaded
as
cross-gen,
that
doesn't,
like
I,
said
a
high
quality,
a
compilation
which
results
in
better
code
that
can
be
better
optimized
so
that
it
runs
faster
and
then
with
this
is
just
the
beginning.
C
The
assumption
is
that
over
time
you
know
it
identifies
things
like
the
hottest
paths
in
your
code.
So
it
will
only
do
this
for
things
that
are
actually
hit,
alright,
close
I'm
in
here
yep
and
then
I
go.
That's
a
convert,
knob
yeah,
I'm,
fig
knob
yeah.
So
that's
seen
the
runt
there's
a
runtime
configuration
file
that
gets
deployed
with
your
application.
When
you
publish
today,
oh.
C
In
settings,
if
you're
so
there's
so
today,
are
you
using
the
see
yes,
so
the
easiest
way
to
turn
it
on
in
RC
is
to
use
an
environment
variable.
Oh.
C
My
god
one
is
that
will
encourage
folks
who
want
to
try
to
have
to
try
it
out
and
if
they
have
problems
will
support
them.
So
it's
not
on
by
default.
But
we
want
people
to
try
it
and
give
us
feedback
as
to
how
well
it's
working
for
their
apps,
because
these
algorithms
tend
to
be
fairly
workload
was
indeed
after
service
website
by
the
way.
C
But
when
we
turned
this
on
in
our
taken
power
benchmark
when
we,
when
we
turned
T
compilation
on
in
the
tech
and
power
benchmarks
for
a
spinet
core,
we
maintained
all
of
the
startup
performance
we
had
from
cost
yen
and
we
recovered
all
of
the
throughput
performance
that
we
had
lost
due
to
cross-gen.
So
we've
literally
got
the
best
of
both
worlds,
which
was
better
than
we
have
a
hope.
A
C
A
This
is
just
like
one
of
a
dozen
or
more
or
dozens
of
cool
things
that
are
happening
into
one
that
are
making
things
just
better
like
it.
Why
is
it
not
to
five?
What
because
it's
such
a
good
thing
is
the
numbers
bigger,
because
there's
so
much
goodness.
Okay,
is
that
house
fo
x,
isn't
timber
like
5.5
is
like
it's
so
good,
okay,
I,
just
think
that
should
be
a
thing.
Yeah.
B
C
So
I
got
a
new
one
for
my
birthday.
I
bought
myself,
a
new
watch,
lovely
and
other
ones
have
gone
away
to
service
and
I
just
stopped
wearing
the
second
one,
just
as
a
trial
and
now
I'm
kind
of
used
to
not
wearing
it.
Yeah
actually
I
stopped
getting
email
on
my
phone
cuz.
They
made
us
install
the
thing
on
our
phone
to
get
email,
so
I,
just
yeah
I.