►
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
I
got
a
bee
in
my
bonnet
about
the
flat
FS
thing
and
hoping
other
performance
for
that
could
be
better,
but
first
I
want
to
know
how
fast
it
can
really
go.
So
I
wrote
some
very
meta
benchmarks,
and
this
is
meant
to
be
a
blind
research
benchmark.
This
is
not
benchmarking,
our
existing
code,
because
that
is
complicated
for
various
reasons.
Don't
get
too
caught
up
on
a
bunch
of
other
details
that
are
irrelevant
and
I
just
want
to
know.
A
How
fast
is
my
file
system
go
flat
out
and
so
to
accomplish
this
I'm,
going
to
kind
of
decide
track
of
a
product
that
is
not
production,
code,
again
kind
of
a
similar
thought,
the
RFC
threat
and
so
I
wrote
a
new
main
thing
and
I'm
trying
to
just
brutalize
the
file
system
and
see
how
it
takes
it.
And
so
this
is
a
ton
of
information
that
comes
out
and
I
have
not
put
these
into
a
nice
graph
yet.
But
the
kind
of
thing
that
I
want
to
get
out
is
like.
A
A
A
So
I
run
this
in
two
different
file
systems
already,
because
my
slash
on
this
computer
is
ax
t4
and
it
is
now
not
running
on
that
fun
story.
I
made
a
mistake
yesterday,
slash
attendance
is
where
one
runs:
benchmarks
right
and
slash
home
if
that's
on
the
same
file
system,
when
you
run
out
of
my
notes,
you're
gonna
learn
some
things
that
don't
work
well.
A
So
now
these
benchmarks
are
running
on
one
of
my
ZFS
partitions
and
the
behavior
of
some
things
is
unsurprisingly
maybe,
but
it's
like
radically
different.
So
operations
is
just
not
the
same.
Also
the
colonel
says
calls
for
things
like
pig
directory.
Tell
me
how
big
you
are
on
ext4.
That
tells
you
how
many
bytes
are
in
all
of
the
structures
or
directory
entries,
and
is
that
a
fast?
It
tells
you
how
many
entries
that
are
you've.