209800+ entries in 0.123s

a111: Logged on 2016-05-12 14:42 asciilifeform: (either
that or
the 'snap4' emulator source code)
phf: your approach
to sourcing
this info is by googling, while actually getting in
touch with people who might know is derided as "whispering". while
the content's been published and public since forever,
those who follow along presumbly knew since
then
☟︎ Framedragger: ~maybe up for it but *that*'d have
to wait
till later
Framedragger: ...yeah, i
think
that
the proper way
to do it
then is
to
take entire disk, populate it with
things
to a high degree and (somehow) with enough spatial dispersion, and benchmark, and restart entire
thing between benchmarks.
mircea_popescu: Framedragger well you pared it down
to ~2 caches, not so bad.
a111: Logged on 2017-03-06 13:10 Framedragger: (just for posterity, other metrics say
that consumer ssds seek average may be ~3ms.)
a111: Logged on 2017-03-11 00:02 asciilifeform: because motherfucking 'people in
the know' whispering like little girls
Framedragger: right, yeah, but
the (really) random seeks.. i hoped
to
tumble it a bit at least
phf: amusingly enough genera's clx is missing some x code for rendering bitmaps. meanwhile clx got ported out, worked on by a dozen of different
teams, gender pronounced and ~still~
that code is missing, with
the same disclaimer
mircea_popescu: it has
the distinction of being fashioned ~entirely out of police blotted / da filings verbatim.
phf: no, just haven't shipped it. i've been waiting for some friends
to do west coast/east coast drive, but
those always seem
to NOT happen when you actually need
them. i can boot it
to do remote x11
though, was configured with
the assumption
that it will boot blind
phf: no no, i'm missing console at
the moment
Framedragger: i must write a short comedy screenplay for how discussions develop in #trilema. "i want
to
take a picture" ... ... ... [intense calculations of incident gamma rays
to reclaim lost pixels in images] [furious rehash of late renaissance representationalism]
mircea_popescu just looked, he is drawing 3.5 kw with his boxen.
this is before ac etc.
Framedragger: asciilifeform: something about needing
to discard 'invalid values' with rdtsc (even when set up correctly - apparently best
to 'pin' particular cpu, etc etc..) oh god.
a111: Logged on 2017-03-10 23:27 asciilifeform: mircea_popescu: aha, i started at one point
to do it, and realized 'wtf why'
Framedragger: asciilifeform: i
thought
that's why folks use CLOCK_MONOTONIC? i guess
the irony is
that it's not..monotonic in
the end, still. :(
Framedragger: ..but if one wants
to measure fs performance, he's stuck with syscalls.
mod6: <+BingoBoingo> Sorry
to hear mod6, keep coming back <+asciilifeform> aha, hats off
to mod6 <<
thank you, Gentlemen.
Framedragger: i actually did check what was available before deciding on clock measurement yknow. but yah, need
to
try rdtsc
Framedragger: incrementor where, in another
thread so
that one may have more context switches for fun?
those calls are blocking..
mircea_popescu: better clock
than ~anything
the kernel exposes, is
the sad
truth\
a111: Logged on 2017-03-06 17:22 mircea_popescu:
the guys did actually splendid work, read
the paper, worth it.
a111: Logged on 2016-09-14 13:28 asciilifeform:
http://btcbase.org/log/2016-09-14#1541639 << not only is
this
true, but you won't be seeing scientifically accurate nanosecond
timing in a konsooomer box at all.
the physical clock is not up
to it.
a111: Logged on 2016-09-14 12:01 Framedragger: "rdtsc is not guaranteed
to be available on every CPU, or
to run at a constant rate, *or be consistent between different cores.*" (emphasis mine). `get_cycles()` is recommended, but from cursory look it seems
that on some architectures it uses rdtsc internally? madness.
Framedragger: ah
that i've heard of. not without its problems iirc
Framedragger: now
they gonna
talk about how one cant measure anything and need phuctor-made superclocks. kk. sure. but
this is as accurate as it gets, sir
mircea_popescu: Framedragger consider using
the recently discussed clocking method
Framedragger: allegedly
this is what folks use for high precision profiling. i checked and wrote
trivial version of
that. but yah, clock_gettime()
mircea_popescu: i do not
trust his clock ; seems
to be accurate within a few ms at best.
mircea_popescu:
time_elapsed_nanos =
timer_end(time_init); <<
trhis is ns precision now ?
mircea_popescu: fopen()
times given 100000000 iterations: min = 1761 ns, max = 1506074 ns, avg = 2326.51 ns, << holy shit what.