log☇︎
228900+ entries in 0.141s
mircea_popescu: ah then not nearly as important.
mircea_popescu: yes but what it uses it for is sorts, select by index may use it if the index is composite.
mircea_popescu: and work_mem should prolly be larger than 4mb, but hard to guess how large without a profile, and this is a major resource consumption ticket, so you actually want to do some maffs.
asciilifeform: mircea_popescu: 0 temp tables
asciilifeform: mircea_popescu: i'd first like to know what this'll do to integrity-on-mains-failure
mircea_popescu: asciilifeform do you use a lot of temp tables ?
asciilifeform: (because apparently 'thousands of queries / sec is abuse, get a cluster' is the 'state of the art')
mircea_popescu: 1) shared_buffers is to be per spec "25% of available ram" ; but it does diminish returns in the gb. you probably have it as 128mb, make it 2gb say.
mircea_popescu: alrighty then let's make a full plan here.
asciilifeform: mircea_popescu: probably. i'ma run with new knob settings as soon as it is safe to reset the db.
asciilifeform: the fastest sync method, supposing one has access to a synced node, but also supposing that it won't do to simply copy the blocks (and it won't, you want to verify) is an eater-shitter system ☟︎
mircea_popescu: incidentally asciilifeform since we're now doing open source db optimization shared_buffers is probably a larger concern. what is it ? defaults to 125mb but i'd readily see it 1-4gb in your case.
mircea_popescu: but you have to have the food.
a111: Logged on 2016-12-30 16:06 mircea_popescu: http://btcbase.org/log/2016-12-30#1593220 << depending on your setup about 40 to 60 days in the wild, about half with ben_vulpes recommended method.
asciilifeform: http://btcbase.org/log/2016-12-30#1593456 << iirc it took me ~3 days to sync via direct eatblock ☝︎
a111: Logged on 2016-12-30 14:32 Framedragger: (do note, 'work_mem' is per user / per request. so may be easier to DoS. thought i should mention this for completeness)
mircea_popescu: http://btcbase.org/log/2016-12-30#1593288 << pretty sure phuctor is 1 user that recycles db connections. ☝︎
a111: Logged on 2016-12-30 14:30 asciilifeform: i'ma try it soon.
mircea_popescu: http://btcbase.org/log/2016-12-30#1593286 << actually workmem should be 256mb especially as you can afford it so totally, go for it. ☝︎☟︎
mircea_popescu: http://btcbase.org/log/2016-12-30#1593252 << these people. if phuyctor is not THE usecase then wtf is. wwwrot ffs. ☝︎
a111: Logged on 2016-12-30 12:28 davout: was there a discussion of the use case where one wishes to create, and sign transactions from an arbitrary set of unspent inputs?
a111: Logged on 2016-12-30 09:13 davout: out of curiosity, how long did it take trb node operators to fully sync?
mircea_popescu: http://btcbase.org/log/2016-12-30#1593220 << depending on your setup about 40 to 60 days in the wild, about half with ben_vulpes recommended method. ☝︎☟︎
mircea_popescu: if he weren't a total fucking retard on top of being a consumate conman, he'd actually have 30k to buy an isp now.
mircea_popescu: and for the record : the dood colluded with sonny vleisides / the rest of the 'ndrangheta running "bfl" scam (which, obviously, the usg hasn't ever prosecuted, in spite of loud violation of, eg, parole termas, because hey, partners in crime) to falsely claim that he received a miner delivery so as to scam bitbet into misresolving a bet, on which they had ~500 btc.
mircea_popescu: oh hey, check it out, irc isn't that important. smart move, barely tolerated fraudster.
mircea_popescu: http://btcbase.org/log/2016-12-30#1593170 << he's not even kidding, i'm going to start banning. ☝︎
mircea_popescu: oh also, friendly reminder today's last day of eulora hackathon. closes in ~11 hours.
asciilifeform has a relative who, until recently retiring, programmed in PL/I ! i shit thee not
asciilifeform: but yes, cpp standardization is beginning to resemble that of PL/I
diana_coman: asciilifeform, to round off: atm eulora code is basically c99 (even that rather reluctantly when we moved over to 64bit)
jurov: i was just paraphrasing, don't remember the exact word
mod6: when I get a free moment, i'll throw the latest eulora on there. can be my mining box. :]
jurov: For the uninitiated, there's already c++17 underway. With folks gearing up to c++23, when We Will Finally Reach Parity With Haskell(noshit).
mod6: i had obsd on it like for nearly all of '16... but wasn't doing anything with it. so i threw linux on there.
mod6: nice! i haven't done any sledding yet. gotta do that one of these times.
diana_coman: how's that eulora-box coming in 2017 mod6 ? :D
diana_coman: got to some snow, sledged downhill, even bruised a knee , got back to peaceful coding now , lol
diana_coman: fwiw I can confirm that current code compiles perfectly fine on gcc 4.4 in any case
diana_coman: basically crystalspace has its own "boost" implementation yes, leaking as expected and on top of that planeshift uses it all over the place quite without any rhyme or reason, adding further to the swamp;
asciilifeform: (which is only half gui toolkit, it is also datastructure lib)
asciilifeform: btw , the unusability of naked cpp was also why we got horrors like 'qt'
mircea_popescu: that's ok, the planeshift implementation leaks at pretty much every other rivet
asciilifeform: jurov: notice how some of the more appealing 11isms (e.g., bounds checking) dun work
asciilifeform: jurov: i am guilty of referring to anything that wasn't in my childhood borland3.1 as cpp11
mircea_popescu: there's two parts to this mess.
mircea_popescu: asciilifeform the client.
asciilifeform: in the old days, every major cpp project had one
jurov: asciilifeform: https://gcc.gnu.org/wiki/C11Status btw, they claim c++11 is fully done in gcc 4.9 (as is my experience) . maybe you meant c++14 ?
diana_coman: asciilifeform, planeshift does that, yes
mircea_popescu: (they did decide to move over to unity last year, then they abandoned the plan._
diana_coman: and it manages to have some half million lines of code doing the job of maximum 100k by the looks of it
mircea_popescu: the quality of code is uneven in the usual foss sense ; its main virtue is that being old, it is mostly not new.
mircea_popescu: asciilifeform planeshift is a mmorpg that the many-eyes beast took 10 years to make. it uses cs which is a sort of game engine, which is built on cal3d which is a gfx lib.
jurov: planeshift is opensource game, crystalspace is the engine
diana_coman: planeshift is an open source mess that was used to jumpstart eulora basically
mircea_popescu: the server code's not published, and the client code is mostly legacy.
jurov: it does not use much c++stdlib, but the crystalspace reimplementation of
diana_coman: asciilifeform, atm we are still slowly, slowly extricating ourselves from the swamps of ps code
asciilifeform: i'ma have to gather the courage and read this thing with own eyes, at some point.
asciilifeform: how about iterators? they are all explicit? million temp vars?
mircea_popescu views with mind's eye diana_coman 's beard growing inches/second in the minds of alf
asciilifeform: so what do the data structures look like ?
asciilifeform: mircea_popescu, diana_coman : so you folx wrote own 'boost'-like horror? fwiw most games firms did, in the golden olden days. my brother's co, for instance, did.
asciilifeform: brings own set of problems. it is where monstrous thigs such as 'boost' came from - lack of cpp11
asciilifeform: because cpp11 is how folx typically end up reluctantly grunting in the stake of gcc5
asciilifeform: btw while we're on this subj, does eulora eschew cpp11?
mircea_popescu: "was gcc 5.x rms approved or not ?" "dude... who cares. it fails to build eulora."
mircea_popescu: note that as time rains on, this sort of query becomes less and less interesting
asciilifeform: 'was this linus-key or linus-flipolade key'
mircea_popescu: sure. i'm not saying it must be standardized. just, there.
asciilifeform: well here's one typical scenario, i find a pgp-signed historic patch (e.g., linus) and want to see what vintage key etc
mircea_popescu: asciilifeform hey, i'm not surfe i want it to work on heathens what.
mircea_popescu: sks was not that fast. or that complete.
asciilifeform: it's a total replacement (if slow) for sks.
mircea_popescu: incidentally, i would say deedbot also counts as tmsr keyserver now.
asciilifeform: most of the time i paste in a key from somewhere, there it is, from april.
mircea_popescu: for that matter they fail to change their own diapers, either, end up having Framedragger write code for them etc.
mircea_popescu: on the other hand submitter support is not mandated, they fail to produce a significant portion of the input.
asciilifeform: the one obvious optimization i was considering was to avoid all dupe checks on key submit and simply deduplicate prior to each bernsteining. but this has serious cost in ui consistency, no more could submitters expect to see a result that is guaranteed to make sense after they submit.
asciilifeform: when you do not know that you oughta restore from backup
asciilifeform: jurov: there is always 'possibility of data loss', machine could be stolen (as it once was!) or burn down
mircea_popescu: yeah it has to catch on eventually.
jurov: asciilifeform: journal is not some magic allowing you to have 100k transactions.second without possibility of data loss
mircea_popescu: i take it you were considering this for next rewrite
asciilifeform: jurov: fs does have the journal
jurov: just a side note - if using filesystem, for ACID guarantee you'd need to flush caches, too
mircea_popescu: does this entirely subvert what phuctor is ?
mircea_popescu: Framedragger think for a second : modulus gets added, it's in cache, other modulus gets added, they don't get checked against each other because one was in cache, now we have two unpopped poppables in db.
asciilifeform: the thing is a 1,001-layer shit sandwich
Framedragger: i suspect then that the inserts/sec slowness is due to postgres currently making really damn sure that *all* layers of cache are forced. this "full forcing of cache for every row" is what makes things slower; but it's also the only really-super-reliable approach for the case at hand (remote box).
mircea_popescu: what you do is not supposed to be predicated on what you can do at any point in your existence.
asciilifeform: Framedragger: may as well run whole thing off a ramdisk then
Framedragger: mircea_popescu: because you could tell postgres to flush rows (forcing all caching layers) every 100 rows, not every 1 row as currently specified
asciilifeform: i'm not convinced that they are separable.
mircea_popescu: the issue is the magic numbers. you said "100". why did you say "100" and how did you [think you] knew ?
mircea_popescu: well not exactly like that, but i guess that may work for a heuristic early on.
mircea_popescu: consider the simple case of "check values, actuate machinery" in article linked here a few months ago. it is quite fundamentally informative.
mircea_popescu: because it is not computer-possible to have what you describe without what i describe.
mircea_popescu: Framedragger see here's what graybeard means : i see that statement, and I KNOW there's a footnote somewhere you don't know about / bother to mention which says "except when abendstar in conjunction with fuckyoustar when it's 105th to 1095th column".