trilemaossasepiatrinquetrilema-hanbotagriculturalsupremacyeuloraspykedlobbespizarro
196d 7h 8m3d 11h 51m82d 9h 21m109d 5h 55m22h 34m13d 1h 39m15h 35m16d 3h 50m77d 4h 58m
krankendenken



lobbes: !!v F67E486876EF654FC1DEB5684A6A8BE1F24B58C4D4F2E925FC580CD2328866CC
deedbot: Invoiced BingoBoingo 0.051 << Buy order # 1055: 500 WFF
asciilifeform: lobbes: i'ma try your proggy tomorrow. ideally time finally came to eat all of the back-archives.
asciilifeform: lobbes: possibly it can even be used to bake a phf-style refill/sync system that eats znc.
asciilifeform: lobbes: http://blog.lobbesblog.com/2019/08/znc2tmsr_etckvvpatch/comment-page-1/#comment-59
diana_alt: so there's still a totally unknown but significant delay on logger, weird stuff
asciilifeform: diana_alt: there defo is. i've measured up to 0.6s (and all outside of the py proggy per se, i.e. vanishes if accessed at localhost )
asciilifeform: diana_alt: fwiw i was not, to date, able to rule out mp's 'overworked pipe' hypothesis .
asciilifeform: when someone sets up this logger outside of piz, i suppose will tell us sumthing re subj.
diana_alt: asciilifeform: hm, does it vanish if accessed from other-machine-at-pizarro too?
asciilifeform: diana_alt: i do not currently know, atm i only have access to 1 piz machine. if you have time, plz try from yours and share result.
asciilifeform: diana_alt: however, if accessed from localhost on ~public port~ (80) then yes same delay
asciilifeform: so i suspect you will find same
diana_alt: asciilifeform: atm all my auth except this travel key are in various degrees of deep freeze but if it's not tested until I get back to my usual terminal, I'll try it out
asciilifeform: delay disappears when accessed on localhost at the 'high' (nonpublic) port where the py proggy itself is answering
diana_alt: interesting at least in re pipe I suppose
asciilifeform: pipe delay ( piz <-> asciilifeform's chair , cannot be generalized to entire planet ) varies from 0.2-0.4s (for revvup of tcp pipe, that is)
BingoBoingo: !!v BF1BCFCD9C0BCE3C6F04BEF6CBC214090B75361B39BE8EEF670BFB6EA52FE42F
deedbot: BingoBoingo paid lobbes invoice 6
asciilifeform: diana_alt: if you press the vtree and set up the logger on own box, where you happen to be, and import the daily db dump, can then observe the 'native' speed of the thing.
asciilifeform: i get (and on rather slow machine) load time for the 'heavy' example page comparable to the time it takes for the mouse button to go up an' down.
asciilifeform: diana_alt: i have plan to move the box to traditional apache, but yet not figured out how to do so w/out unacceptably long disruption of service .
asciilifeform: ( at one pt, long ago, when baked phuctor, asciilifeform had a preference for nginx, but it turned out to be ill-founded . currently both phuctor and log www are served by a nginx . )
asciilifeform: neither phuctor nor logger is written in such a way as to force the choice of either nginx or apache as the front-side proxy, will eat either just the same. simply requires the appropriate config.
asciilifeform: the reason why i currently suspect nginx as the culprit, is that i observed very similar delay when loading static (e.g. FG photograph) files via same.
asciilifeform: previously i chalked this up to 'slow pipe'. now suspect also the proxying proggy.
asciilifeform: ( had not, prior to folx observing 'logger is slow, say wai' , taken the sweat to properly monitor where in the typical page load is time spent and on what )
diana_alt: ah, I *was* wondering re nginx as my only recollection of it was BingoBoingo trying it out and ending up with more trouble than it's worth
asciilifeform: BingoBoingo: plz perform the simple experiment suggested by diana_alt and tell result.
snsabot: Logged on 2019-08-19 13:53:04 diana_alt: asciilifeform: atm all my auth except this travel key are in various degrees of deep freeze but if it's not tested until I get back to my usual terminal, I'll try it out
diana_alt: spyked: I don't recall and can't see at http://thetarpit.org/posts/y05/081-feedbot-manual.html - is feedbot for L1 only or does it work for anyone with positive ratings or regardless of rating or what?
diana_alt: ah, nm, now I saw it in the footnote - it is L1 only
asciilifeform: diana_alt: reasons to suspect the pipe, include this: i have stood up temporarily a raw flask on port 33. try time curl "http://logs.nosuchlabs.com:33/log" > /dev/null
BingoBoingo: diana_alt: I never managed to deploy anything that worked as needed on nginx. I managed things that almost work on lighttpd, but it simply lacks the good stuff apache offers for blogs.
asciilifeform: ( diana_alt lemme know after tried, i'ma switch it off, it's an unhygienic thing )
asciilifeform: in my own test, there is no substantial detectable diff
BingoBoingo: asciilifeform: http://p.bvulpes.com/pastes/0I7Gg/?raw=true
diana_alt: asciilifeform: http://p.bvulpes.com/pastes/kYos2/?raw=true
asciilifeform: ( keep in mind that the links in the loaded page still point to the original )
asciilifeform: diana_alt: do 3-4 shots via each (main vs 33) and paste plox
diana_alt: asciilifeform: http://p.bvulpes.com/pastes/kUEXH/?raw=true
BingoBoingo: asciilifeform: from Pizarro machine http://p.bvulpes.com/pastes/6jrpH/?raw=true
asciilifeform: ty diana_alt , BingoBoingo . (i'ma switch off the 2nd logger for nao, will run it again if anyone requests, later)
asciilifeform: BingoBoingo's output is pretty interesting -- how is it that he gets >2x the wait from ~local~ machine than diana_alt from europistan.
asciilifeform: ( possibly BingoBoingo's is under load ?? )
BingoBoingo: Possible, don't have ssh into any cabinet machines that aren't serving things
asciilifeform: diana_alt's, on other hand, is very similar to mine, i.e. no substantial diff b/w main and 'naked'
BingoBoingo: asciilifeform: meanwhile trying on other machine seems solved for the right reason "rl: (6) Could not resolve host: logs.nosuchlabs.com"
asciilifeform: BingoBoingo: naked ip also worx (lemme know if you want the 2nd logger on 33 switched on , to try moar )
asciilifeform: the logger does not depend on dnsism to work ( can set the domain in /etc/hosts like e.g. mp does )
BingoBoingo: asciilifeform: I don't think that will be needed http://p.bvulpes.com/pastes/05a8I/?raw=true
BingoBoingo: "real 0m 0.01s"
asciilifeform: BingoBoingo: the 33 logger is off atm
BingoBoingo: right, these are tests on the one that's running
BingoBoingo: From other machine time goes up a smidge: "real 0m0.035s"
asciilifeform: BingoBoingo: that loox realistic.
asciilifeform: ( and imho further suggests that pipe is culprit )
asciilifeform: 'go to war with the pipe you have, not the pipe you wish you had'(tm)(r)
asciilifeform: piz pipe is not gonna set any speed records. (however, is extremely reliable, e.g. asciilifeform gets ssh sessions that last 3-4 months)
asciilifeform: ... and typically they die on acct of connectivity pause on asciilifeform's end, rather than piz
asciilifeform: !quptime
snsabot: asciilifeform: time since my last reconnect : 3d 4h 43m
asciilifeform: ^ the log bot itself, for instance, thus far has only reconnected when asciilifeform manually cycled it, to update to new ver (last such time, to put phf's uniturd pill in production)
BingoBoingo: <asciilifeform> ( and imho further suggests that pipe is culprit ) << My desk offers "0m0.073s" suggesting geography may be at play
asciilifeform: interesting.
BingoBoingo: I remember a thread from last year where trinque saw long pings doing something at the same time MP was enjoying incredibly fast ping to Eulora server
asciilifeform: oook here's an experiment : asciilifeform set up a mirror of the logotron on a cheap heathen host. ( one of the most rubbish hosters known, lulazon's . hence cannot in fact stand up copy of bot there, fleanode bans conns from it unless sslized. but the db is current. )
asciilifeform: time curl http://54.209.217.34/log > /dev/null from my chair yields 0.063s.
asciilifeform: other folx welcome to try. e.g. the 'heavy page' : curl http://54.209.217.34/log/trilema/2018-04-18#1802801 > /dev/null
asciilifeform: ... from here eats 0.268s.
asciilifeform: deliberately this setup uses nginx and same (as far as could replicate on the heathen box) stack of proggies as the orig.
asciilifeform: this suggests that culprit of 'mystery delay' is in fact piz pipe.
asciilifeform: errybody's welcome to play with the mirror ( it's a '1st month -- phreeee!' pseudo-machine , i'ma leave it up for a spell, tho it will , obv., grow no new log lines )
asciilifeform: i suppose for completeness will mention an alt-hypothesis -- somehow nic on dulap is culprit.
asciilifeform did not bother to sync the clock, so times on shit mirror will vary vs. dulap's
asciilifeform: all knobs aside from 'download snapshot' work, so feel free to e.g. walk the 'random' pages etc.
asciilifeform: this experiment also reveals that asciilifeform's logotron will in fact stand up, with no modifications, on a python, flask, pg, etc. plucked out of arbitrary rubbish bin.
asciilifeform: i'ma switch this thing off in coupla days, once errybody's taken the offered measurement and is satisfied ( i dun want a 'fossilized' logger sitting for idiots to find and think 'they're dead' )
asciilifeform: BingoBoingo, diana_coman, et al ^ as time permits , plox to post load times of this ^ log.
asciilifeform brb,teatime
BingoBoingo: asciilifeform: My chair gives "real 0m0.524s"
BingoBoingo: From the rack gives 0m0.561s
asciilifeform: BingoBoingo: hard to say for fact, but seems to add up to a picture where's there's a ~0.5s bottleneck b/w south amer. and errywhere else.
asciilifeform: ( in the mirror example, we get it in the reverse direction, but seems to be that same ~0.5s ! )
asciilifeform: other folx btw are encouraged to perform similar experiment ; whole thing took me approx 35min of meat time, from revving up heathen pseudo-box to posting link here.
asciilifeform: ( of which ~8m spent downloading db snapshot from piz )
asciilifeform: ( the rest -- largely, hand-copying configs )
asciilifeform: http://logs.nosuchlabs.com/log/trilema/2019-08-19#1929694 << this is worth expanding on. asciilifeform also gets very fast pings ( never moar than 200msec, to date ) and fast udp. what i suspect is, usg's snoop gear that sits as parasitic toad on south amer's pipe, specifically slows down tcp.
snsabot: Logged on 2019-08-19 16:13:02 BingoBoingo: I remember a thread from last year where trinque saw long pings doing something at the same time MP was enjoying incredibly fast ping to Eulora server
feedbot: http://qntra.net/2019/08/200-us-ceos-sign-pantsuit-pledge-declaring-primacy-of-social-and-political-goals-after-other-us-ceo-confirms-usg-malice-pursuing-said-goals/ << Qntra -- 200 US CEOs Sign Pantsuit Pledge Declaring Primacy Of Social And Political Goals After Other US CEO Confirms USG Malice Pursuing Said Goals
BingoBoingo: !!invoice bvt 0.002 Shared Hosting Monthly
deedbot: Get your OTP: http://p.bvulpes.com/pastes/SUH6v/?raw=true
BingoBoingo: !!v 05D3990D06D8604953F6C828348B6956D7C82A6BF7375DC138C40FC84F3712A7
deedbot: Invoiced bvt 0.002 << Shared Hosting Monthly
BingoBoingo: !!invoice diana_coman 0.10429931 Rockchip w/ FUCKGOATS, Annual, Through July 2020
deedbot: Get your OTP: http://p.bvulpes.com/pastes/Uf5wc/?raw=true
BingoBoingo: !!v 0E9B87B89855B52F22131F73CD3112CEB038FAC0F821A59E81B19AB9CB0635FA
deedbot: Invoiced diana_coman 0.10429931 << Rockchip w/ FUCKGOATS, Annual, Through July 2020
BingoBoingo: !!invoice jurov 0.01445328 TBF Colocation August 2019
deedbot: Get your OTP: http://p.bvulpes.com/pastes/W1gQ3/?raw=true
BingoBoingo: !!v 605B8E12B4D1074B3A8451A03A52D9DE223EAFCCA51DB6B4AE77EBAB9DB1A3B5
deedbot: Invoiced jurov 0.01445328 << TBF Colocation August 2019
BingoBoingo: !!invoice lobbes 0.02894981 Rockchip and Shared Hosting Quarterly
deedbot: Get your OTP: http://p.bvulpes.com/pastes/EIf2i/?raw=true
BingoBoingo: !!v FA9AF8DAE08C5B74E08025B8F0657CFEB8CF38B393BD5D77B2956CEC87B5EAB7
deedbot: Invoiced lobbes 0.02894981 << Rockchip and Shared Hosting Quarterly
BingoBoingo: !!invoice trinque 0.01645328 Colocation + Shared August 2019
deedbot: Get your OTP: http://p.bvulpes.com/pastes/5HYsI/?raw=true
BingoBoingo: !!v F8F948D9C87A8961B10AACDAAA84CAD85170F00682E89051933F7285937831B5
deedbot: Invoiced trinque 0.01645328 << Colocation + Shared August 2019
lobbes: http://logs.nosuchlabs.com/log/trilema/2019-08-19#1929696 << from my chair here in North Carolina Usgistan, my 'real' is 0m0.227s
snsabot: Logged on 2019-08-19 16:37:04 asciilifeform: time curl http://54.209.217.34/log > /dev/null from my chair yields 0.063s.
lobbes: from my EDIS VPS (in Austria iirc) I get 0m0.376s ; from piz rockchip I get 0m0.579s
lobbes: Numbers for the 'heavy log' as follows: NC chair 0m1.055s ; Euro VPS 0m0.971s ; Piz Rkchp 0m1.435s
lobbes: !!v 86AC694AC6B7EB77DB8570DBD1566EB3A30F5D5BFCA6BF47CE01B409A968F55C
lobbes: trinque: ^ I may have been too quick on the draw when deedbot came back online. plox to lemme know if I should re-issue the above !!v
lobbes bbl
asciilifeform: ty for the timings lobbes . seems to match up with asciilifeform's and BingoBoingo's pictures
asciilifeform: ( i.e. pretty fast connection reich <-> reich ; palpably slower piz <-> reich )
asciilifeform: BingoBoingo, lobbes , et al : i'ma leave the rubbish box to run until further notice, and give it cron job that eats db from dulap erry day .
asciilifeform: ftr gets ~80kB/s avg. from dulap, there.
asciilifeform: keep in mind that bot will not echo log lines cited from rubbish mirror. it is fit strictly for timing experimentation.
asciilifeform: the 'db snapshot' link nao worx. this box will do duty as an (unauthoritative!) 'fast' mirror of db snapshot also, until someone comes up with better.
asciilifeform: for n00bz : the cron job script which powers this ; the cron job itself .
asciilifeform: BingoBoingo: this remains a mystery. i gotta wonder if there's something peculiar re our routing, which gives this effect.
snsabot: Logged on 2019-08-19 13:52:44 asciilifeform: diana_alt: however, if accessed from localhost on ~public port~ (80) then yes same delay
asciilifeform: BingoBoingo: from this pt i'ma follow the prescription mp gave during last 'wai slow' thrd -- leave it alone, there aint much to be done re to speed it up ( as imho conclusively showed that the pipe is to blame ). will move on to other matters ( import of historic logs ; fix of reported catastrophic bugs, incl. the resync of numeration mp asked for ; and then to get back to ffa ! )
asciilifeform: rly what we oughta have is 7+ ~active~ bots/logotrons on 7 continents, then no one will have to grumble 'wai slow'
asciilifeform: i expect at some pt mp will say to anyone in l1 who aint running a logger, 'партбилет на стол!'(tm)(r)
asciilifeform: btw for thread-completeness, heavy page loaded locally on the shitbox consumes avg. of 0.2s.
snsabot: Logged on 2019-08-19 16:38:17 asciilifeform: other folx welcome to try. e.g. the 'heavy page' : curl http://54.209.217.34/log/trilema/2018-04-18#1802801 > /dev/null
asciilifeform: (i.e. all on top of this, is transmission delay from east amerireich, where thing sits.)
asciilifeform: i.e. takes ~0.068s to travel the 50km or so to asciilifeform's chair from said pseudobox.
snsabot: Logged on 2019-08-19 16:38:26 asciilifeform: ... from here eats 0.268s.
asciilifeform: meanwhile, loox like lobbes reproduced asciilifeform's orig. observation.
asciilifeform: ^ dulap incidentally performs considerably better , unsurprisingly, than the pseudo-sadmachine, in re actual page generation on local end.
asciilifeform bbl:meat.

Random(trilema) | Download daily DB snapshot | Get Source Code