►
Description
The Pipeline Execution team launched an experiment on Gitlab.com adding a "Performance Insights" button to the pipeline details page.
This will be live until September 22, 2022 at which point the button will be disabled. We would appreciate feedback from the wider community while this is live.
You can leave feedback for us in this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/365902.
Thanks!
A
A
A
I'll
talk
about
that
a
little
bit
more
in
just
a
minute
so
clicking
on
that
will
get
you
some
data
about
that
specific
pipeline,
showing
you
the
five
slowest
jobs
in
the
pipeline,
the
job
that
was
in
queue
the
longest,
how
long
it
waited
before
it
started
its
execution
and
the
very
last
job
that
ran,
and
so
this
will
link
you
into
job
details.
If
you
click
on
one
of
the
jobs,
you
can
take
a
closer
look
at
how
long
it
ran.
A
Maybe
what
is
causing
it
to
run
long
same
thing
with
the
longest
cue
job
and
then
the
last
executed
job
that
will
show
you
the
dependencies
there.
So
I
wanted
to
show
that
off
because
we're
running
this
as
an
experiment
and
as
part
of
that
we
have
a
feedback
issue
which
will
be
linked
below
the
video
here.
A
So
we
want
to
hear
from
you
users
what
you
think
about
this,
and
so
I
want
to
explain
a
little
bit
about
why
we're
running
this
as
an
experiment
and
why
there's
this
pipeline
or
why
there's
this
feedback
issue
out
there,
so
we
want
to
learn
more
about.
Is
this
kind
of
data,
something
that
users
want?
Do
you
find
it
valuable,
because
if
not
we're
going
to
turn
this
off
and
that's
currently,
the
plan
is
on
september
22nd?
We
will
disable
this
feature
and
we'll
be
removing
the
code.
A
A
How
long
we're
going
to
be
running
it
and
what
we
might
be
doing
next,
which,
as
of
right
now,
is
nothing
we're
running
this
as
an
experiment
like
I
said
to
understand,
if
it's
valuable
to
you
users,
you
can
always
check
in
on
where
we're
going
next,
what
we're
building
next
on
the
direction
pages
for
the
two
categories:
continuous
integration
and
merge
trains,
though
that
pipeline
execution
works
on,
and
so
what
kind
of
feedback
do
we
want?
You
know
general
thumbs
up
thumbs
down,
are
super
valuable
to
us.
A
A
Suggestions
for
improvements,
please
post
those
there,
and
if
you
see
something
that
matches
up
to
your
experience
and
either
of
those
threads,
giving
it
a
thumbs
up
or
a
plus,
is
a
great
way
to
indicate
to
us
that
you're
getting
some
value
out
of
the
feature
or
you're
trying
to
use
it,
but
you
saw
the
same
bugs
as
well.