3700+ entries in 0.018s
Framedragger: asciilifeform: any JOINs in those multiple queries for each 'insert'? (if yes, this param should help.)
Framedragger: (do note, 'work_mem' is per user / per request. so may be easier to DoS. thought i should mention this for completeness)
☟︎ Framedragger: (some of those settings don't require db restart (but may require to 'flush' params), some of them do, best to restart db after all changes are made.)
Framedragger: ah hm. tbh i'd still change work_mem because it's ridoinculously low by default, but i hear ya.
Framedragger: work_mem (used for in-memory sorts) is 4 MB default. 4 MB. (9.5 anyway). set it to 50 MB as per advisory at least.
Framedragger: ahh right, i assume those include in-memory sorts
Framedragger: mircea_popescu: it's dark here in the northern hemisphere, god it's deperessing :( mornin'..
Framedragger: asciilifeform: i take it you are certain that main bottleneck and 'hogger' is the numerous inserts?
Framedragger: to be 100% certain, i'd have to check. i see your concerns.
Framedragger: right. i just thought about checkpoint_completion_target (set to say 0.9) which may help with inserts, but ultimately you're right, physical reality
Framedragger: busy for a bit, i don't want to cite you sth without thinking about it
Framedragger: i'm thinking,more memory could help with certain things that db is busy with, incl insertion, even. i'm not sure.
Framedragger: aha right. i'm doing sth else but i could later ping you with a sample postgres file which you could try out (would need db restart)
Framedragger: it's something that can be very easily changed and tested without sweat or breaking things.
Framedragger: asciilifeform: do you have an idea how much memory you could allow postgres to eat up? i know you have that other super hardcore thing eating lots of memory on the side
Framedragger: (i'm thinking about things like size of shared buffers etc)
☟︎ Framedragger: would still be interested to take a look, wouldn't hurt.
Framedragger: i wasn't going to show that she was doing good crypto. but this is definitely doing crypto :) (unless goalposts shifted again, etc)
☟︎ Framedragger: and ecc, i wonder where your wrath was towards bitcoin, in that regard. (i am aware that you were never a bitcoin enthusiast tho, so there's that)
Framedragger: she wrote current version of, and afaik (maybe old info) still maintains tor bridge infrastructure. at the very least includes saltmining with 'cryptographers' and implementing their ideas (not whole cryptosystems), unless saltmine implies academia
Framedragger: mircea_popescu: ah, that *is* a nice way of putting it. but then, it's a much weaker assertion than "define cryptoperson as someone who's heard of phuctor" :)
Framedragger: asciilifeform: airgap solution guy or someone else? just curious
Framedragger: but it is a bit funny how all of these "is element part of this precious set" functions defined in tmsr yield elements only from tmsr. you'd say that's not a problem, but you know.
Framedragger: that's not an altogether bad attitude now, is it. but yes she's paying for using python 3
Framedragger: i'm pruning trustleaves slowly, but yeah need another degree of rigour hm
Framedragger: i did learn that if i don't flush out the funny parts i'll just grow up to be someone with no interior at all. :)
Framedragger: right. and it's valid, i can't really defend it properly
Framedragger: (also apologies if my continued presence renders a constant source of radiation damage)
Framedragger: (fwiw i wouldn't defend tptacek as much, at all, but i can see how these framedraggerisms can be related under same umbrella)
Framedragger: phf: fair. with regards to chatting up it was more to do with me not being involved with tor anymore; but even that particular still stands, so yes fair
Framedragger: one or two. i know both. the other guy is a guy
Framedragger: (and no it's not a 'formal proof' i know.. :/ )
Framedragger: person with current root access to tor boxen in bridge infrastructure = person sitting here and teaching me stuff, etc
Framedragger: person who signed all $project-committed code = person standing in front of me, etc.
Framedragger: oh you're saying 'isis' doesn't have a good referent. i agree. she has a pgp key alright.
Framedragger: (obvs i'm not defending her being core part of tor, or tor.)
Framedragger: her handle is 'isis agora lovecruft', it's a pseudonym, retarded or not, like framedragger
Framedragger: well look at what she's done if you'd like, i'm not saying you'd have to meet her in person
Framedragger: what i'm saying is that she actually does crypto. if you shift goalposts, whatever
☟︎ Framedragger: you haven't met her in person, you don't know.
Framedragger: trinque: you referring to moxie i'm guessing :D
Framedragger: this isis girl in tor reads crypto papers and implements them and runs their bridges infrastructure which uses its own nifty things (hashrings for distributing bridge nodes etc), i'm quite certain she hasn't heard
☟︎ Framedragger: well if you define 'vaguely involved with crypto' as per tmsr-usual "has WoT presence" then yeah
Framedragger: asciilifeform: you really think everyone in h4cker kommunity is aware of phuctor?
Framedragger: mircea_popescu: media.ccc.de is 195.54.164.138
Framedragger: README says "the code that can be found here is the code that is used for election" so that's sorted......
Framedragger: heh, speaking of 'provably fair' and location in question (tallinn), they've been doing e-voting (for all major elections etc) for a few years now. iirc code audits showed weak spots, multiple sek0rity expert teams, advisory bodies etc recommended to shut it down because it was unsafe, but proud estonia knows better.. :p
Framedragger: pretty cool images, some of these. weirdly artistically stimulating
Framedragger: not enough butt-sniffing, so maybe that's a no.
Framedragger: given that this is in san francisco, am i looking at a typical californian startup hackaton here?
Framedragger: hm. i still run one (low bandwidth), would be interesting to check things i suppose..
Framedragger: also, as you noted earlier, there's a good chance a bunch of ssh *client* keys were generated on those machines, too, so also possible to try to bruteforce-login with generated keys (to servers which have broken rngs)
Framedragger: oh god i hear mircea_popescu's mind-cpu resetting :(