430600+ entries in 0.295s
BingoBoingo: Well malloc()
tends
to aggressively
try
to keep shit from running into each other
mircea_popescu: if my suspect is
true,
this very neatly shows openbsd as a superior os.
BingoBoingo: <mircea_popescu> BingoBoingo i suspect obds SANE. ie, it forces
the allocation. << It does for most
things.
mircea_popescu: BingoBoingo i suspect obds SANE. ie, it forces
the allocation.
BingoBoingo went from fairly stable 224-236 MB of ram usage
to a very flat 986 MB
the very flat makes me suspect OpenBSD weird
BingoBoingo: At least I killed
the orphanages earlier
this week
mircea_popescu: i dunno where erryone else shops for intertubes
that work
mircea_popescu: lol now my node is getting
teh silent intertubes
treatment
BingoBoingo: Random
turd. Could be OpenBSD memory handling weird
BingoBoingo: pete_dushenski:
There's a second one a bit later
mircea_popescu: asciilifeform anyway, im bringing
the original node back on
to help along.
mircea_popescu: i gotta confess watching
the idjits squirm is kinda fun.
BingoBoingo: I just have
to wonder what idiocy is going
to break everything
the first weekend of September
BingoBoingo forgot
that when you change versioning
this whole
thing wants rebuilt again
mircea_popescu: because
they're running "the newest version" which "always works". in
the sense of not.
BingoBoingo: lol bc.i fixed
their shit and got constipated again
BingoBoingo: Fuck it. Imma report a whole number version
this
time
mircea_popescu: it'll be indeed a hard
task
to explain
to one's grandkids
to what end does bitcoind actyually use
threading
BingoBoingo: <mircea_popescu> version 99992 lol << Was me. Since I dumped
that debug.log
took it down
to rebuild with new identity.
mircea_popescu: whjy use static buffers when one can be a danger
to
the system
mircea_popescu: iirc bdb just makes assumptions about what memory it may allocate and dies at
the later
time if
they get contradicted
mircea_popescu: im pretty certain said magic numbers actually make it impossible for a block
to be crafted legally and still crash your bdb, soi
there's
that.
BingoBoingo: <mircea_popescu> version 99992 lol << What's
the rest of
the version?
mircea_popescu: anyway
there's a reason for
the magic numbers
too, something
to do with
theoretical maximums of a 1mb block but i don't recall what
THAT was either.
punkman: asciilifeform: you'll have
to add it
assbot: Logged on 05-07-2015 15:33:42; asciilifeform:
http://log.bitcoin-assets.com/?date=04-07-2015#1187470 << what i was saying
there bears repeating. if we had a fleet of pogos deployed,
they would ~all~ be paperweights now. and for so long as we use
the cpp
turd,
there can be no guarantee of
this kind of
thing not happening in
the future.
mircea_popescu: <danielpbarron>
the gnomes figured out a magic amount of bytes
that got accepted by some but not all, except it seems
their beloved bc.i got caught in
the fire << bc.i gets caught in every fire.
cazalla: and
they all give
the expected response of "i'm gonna
think about my food more often in future" instead of hey, imma get some chickens and do
this at home
cazalla: punkman, what a lost generation, can't even kill a chicken without getting out
their phone
to post it on fkn instagram
punkman: max locks: "
This value is used by DB_ENV->open
to estimate how much space
to allocate for various lock-table data structures"
punkman: this probably comes from derpy indexes and structures used by bitcoind, not
the blockchain
trinque: I modeled
this
thing with ben_vulpes one day on a whiteboard;
the blockchain is not an impossibly complex data structure
trinque: at least in
this conversation we *are*
talking about databases;
the above is insanely shit
trinque: again, what is it doing locking
that many records at once?!?!
trinque: asciilifeform | BingoBoingo: is
there a particular reason we didn't set
that knob
to maxint ?
Luke-Jr: asciilifeform:
that's (partly) why we moved
to LevelDB ;)
BingoBoingo: asciilifeform: I
think we just copied
that number from some patch Luke-Jr pointed us
to
BingoBoingo: asciilifeform: I just upped
the DB shit
to 80000, backed up my blockchain, and recompiled
decimation: "They also pointed out
that
the aircraft is still under development and
that full production is not scheduled until 2019, 17 years after
the program’s inception. And
they wondered whether
the Pentagon really need 2,443 of
the planes “in light of countervailing pressure
to reduce force structure
to conserve resources.”"
assbot: The Marines say
the controversial F-35 fighter is now ready for combat. Now what? -
The Washington Post ... (
http://bit.ly/1JCd5HZ )
BingoBoingo: asciilifeform: record setting numbers of
transactions in blocks
BingoBoingo: punkman: Unwedged 0.7-ish stator still isn't anywhere near
this sync'd yet
punkman: trinque: is
that still on btcd?
punkman: so
they got wedged pretty bad?
punkman: "Blockchain.info is currently down for maintenance. For status updates please see
Twitter. Apologies for any inconvenience. "
punkman: you gotta read BDB code for
those locks
decimation: I'm not sure on
that point, would need
to read
the code
trinque: I'm reading
through
the code, just
trying
to prime on whatever knowledge is handy
decimation: I can't enumerate
them all, but
the network code, for instance, runs in a different
thread
than
the db code for instace