log☇︎
164 entries in 0.565s
assbot: Logged on 07-05-2015 15:19:45; mod6: asciilifeform: just to be clear, all of your vagrind runs against bitcoind are: v0.5.3.1+Orphanage_ThermoNuke ? Or just plain v0.5.3.1 ?
mod6: asciilifeform: just to be clear, all of your vagrind runs against bitcoind are: v0.5.3.1+Orphanage_ThermoNuke ? Or just plain v0.5.3.1 ? ☟︎
mod6: <+asciilifeform> [BTC-dev] Full Orphanage Thermonuke DHAT Output. << nice work! thanks :]
asciilifeform: [BTC-dev] Full Orphanage Thermonuke DHAT Output.
mod6: <+asciilifeform> [BTC-dev] Full Orphanage Thermonuke Massif Output (without 'pages as heap' flag) << thanks asciilifeform!!
asciilifeform: [BTC-dev] Full Orphanage Thermonuke Massif Output (without 'pages as heap' flag)
mod6: asciilifeform: here's an update as to where my test of v0.5.3.1+Orphanage_Thermonuke is at: http://dpaste.com/3J5K2JB.txt
ascii_field: mircea_popescu: take a few min. to read the patch, if you have not. the behaviour should be logically equivalent to virginal 0.5.3 with an orphanage of zero
ascii_field: mod6: aha i asked because you specified 'orphanage burner' - which was the 1st try of this
mod6: ascii_field: I'm running with this patch: http://therealbitcoin.org/ml/btc-dev/attachments/20150504/asciilifeform_orphanage_thermonuke_2d219fdd1a0da960be38797566e9c0820df11ce6.patch
mircea_popescu: http://log.bitcoin-assets.com/?date=06-05-2015#1122508 << yes. because for all the pretense of "development" and "progress" and "new versions" and of course "blockchain technologees" of the #bitcoin-dev muppet orphanage, THEY.HAVE.NOT.ACTUALLY.DONE.ANYTHING. ☝︎
mod6: <+asciilifeform> [BTC-dev] Full Orphanage Thermonuke Massif Output (Theoretically, covers entire address space of process) << great work, asciilifeform. thanks for putting that together :]
asciilifeform: (the 'orphanage burner' one)
davout: not sure i get "the thing walks the orphanage and finds the start of the chain"
asciilifeform: we don't have an orphanage any more
asciilifeform: 2) after this, when bastard block comes in, the thing walks the orphanage and finds the start of the chain, and asks for its antecedents.
asciilifeform: [BTC-dev] Full Orphanage Thermonuke Massif Output (Theoretically, covers entire address space of process)
asciilifeform: [BTC-dev] Full Orphanage Thermonuke Valgrind Output.
davout: asciilifeform: really curious to see how the orphanage thermonuke patch will work in the field
assbot: Logged on 05-05-2015 01:32:31; mod6: ok bitcoin-v0_5_3_1 + Orphanage Nuke is running with `nmon -f -s3` & `vmstat 1`, so we should have some good metrics when complete.
mod6: 9d7cab14db48000ed91d12301f19341ce55e86fe919922f8a4f80f49625b881b296deb037d35ef899996e097b4f1c0ab5a035c2ced04758b9838f3924ce4ed78 asciilifeform_orphanage_thermonuke.patch
mod6: # sha512sum asciilifeform_orphanage_thermonuke.patch
mod6: ok bitcoin-v0_5_3_1 + Orphanage Nuke is running with `nmon -f -s3` & `vmstat 1`, so we should have some good metrics when complete. ☟︎
asciilifeform: sha512(asciilifeform_orphanage_thermonuke.patch) == 9d7cab14db48000ed91d12301f19341ce55e86fe919922f8a4f80f49625b881b296deb037d35ef899996e097b4f1c0ab5a035c2ced04758b9838f3924ce4ed78
asciilifeform started valgrindized run of thermonuked-orphanage tester
danielpbarron: mod6, http://danielpbarron.com/asciilifeform_orphanage_thermonuke.txt
mod6: -rw-r--r-- 1 root root 4007 May 5 00:19 asciilifeform_orphanage_thermonuke.patch
mod6: curl -s http://therealbitcoin.org/ml/btc-dev/attachments/20150504/asciilifeform_orphanage_thermonuke_6f320afb2423a2892d89e855829e3915c8b7a170.patch.sig -o asciilifeform_orphanage_thermonuke.patch.sig
mod6: curl -s http://therealbitcoin.org/ml/btc-dev/attachments/20150504/asciilifeform_orphanage_thermonuke_2d219fdd1a0da960be38797566e9c0820df11ce6.patch -o asciilifeform_orphanage_thermonuke.patch
mod6: <+ascii_field> [BTC-dev] (EXPERIMENTAL) Full Orphanage Thermonuke. << Just saw this on the train & read patch. Great work!
ascii_field: [BTC-dev] (EXPERIMENTAL) Full Orphanage Thermonuke.
mircea_popescu: "a bitcoind (pseudo-static, portatronic, orphanage-burner patch with max-bastard constant value of 5 running on pogo, heathen linux.)" << i lelled.
asciilifeform: [BTC-dev] Process mem. stats from heathen pogo running ineffectual orphanage burner (max==5)
asciilifeform: its a standard skull'n'crossbone orphanage burner with max cap set to 25
BingoBoingo: asciilifeform: The orphanage burning version, see if stable.
thestringpuller: you told me not to patch in orphanage burner yet.
asciilifeform: thestringpuller: the idiot crashy one ('classic', with memleak) or the one with questionable patch ('orphanage burner') ?
asciilifeform: classical or orphanage-burning ?
asciilifeform: dove in once or twice to fish out the orphanage burn thing
assbot: 6 results for '"orphanage burner"' : http://s.b-a.link/?q=%22orphanage+burner%22
the_scourge: !s "orphanage burner"
mod6: ah, my mistake. ascii numbered the "Orphanage Burner" as v0.5.3.2
punkman: danielpbarron: this one? "bitcoin-armv5-bastard includes the 'orphanage burner'"
punkman: danielpbarron: with orphanage burner?
asciilifeform: mod6, danielpbarron: in case this wasn't clear, my armv5 build still has the checkpoints (other than orphanage burner, only the basic patches are in)
asciilifeform: http://therealbitcoin.org/ml/btc-dev/attachments/20150130/asciilifeform-orphanage-burner_80eb450469d93b270aa160e26b4cdab732add2c4.patch
asciilifeform: mircea_popescu, davout: look through orphanage for % of blocks more than 10% off the difficulty << interesting idea
mircea_popescu: asciilifeform if you feel like testing a 3rd approach, can you look through orphanage for % of blocks more than 10% off the difficulty ?
mircea_popescu: <asciilifeform> the logical thing to do, for it, would be to jettison the entire orphanage if approaching the hard limit << this may be a good idea, if actually something's needed.
asciilifeform: not in the experimental 'orphanage burner' build
asciilifeform: the logical thing to do, for it, would be to jettison the entire orphanage if approaching the hard limit
asciilifeform: inference, with only a small leap, is that orphanage-burner testatron would have oomkilled precisely one time, had it ran under 128M constraint
asciilifeform: based on the footprint, the orphanage burner functions
asciilifeform: bitcoind limited to 'orphanage' of 50 blocks (running on ordinary pc) never syncs
mircea_popescu: like, the Brock Pierce memorial orphanage ?
BingoBoingo: What about most ridiculous hardware running a full node. I imagine someone submitting an orphanage could win that.
mircea_popescu: wasn't he like rescued from a romanian orphanage by some french ppls ?
mircea_popescu: who apparently grew up in a romanian orphanage (?!)
mircea_popescu: Apocalyptic: "mark karpeles was raised in a romanian orphanage" << wait, WHAT ?!
Apocalyptic: "mark karpeles was raised in a romanian orphanage" // mircea may have some insights on that
Vexual: its sad that one can' give money to an orphanage in cambodia without a thought
jcpham: i steal power from the orphanage
jcpham: I steal power from the local orphanage
jcpham: i'm going to keep mining as long as the orphanage is paying my power bill