asciilifeform: diana_coman: a proggy is an 'ideal object', almost anyffin, within obv limits of algo complexity is 'possible'. but in actual practice 'notation is worth 80+/-iq' and some notations make folx into effectively downs syndrome sufferers when the # of moving parts crosses certain threshold
asciilifeform: http://btcbase.org/log/2019-01-22#1889097 << with engine, you can compute the efficiency ( joules out / joules in ) and even get ~exact estimate of how much useful work engine of particular size will do. but with shitware..☝︎☟︎
asciilifeform: BingoBoingo: and no it aint a 'industrial' pipe, with asn etc. which is why i marvel, that it closely approximates one functionally, despite the cheap.
asciilifeform: cache only affects public/allcomer resource.
asciilifeform: BingoBoingo: how does it cache the e.g. tB of rng i happen to generate in racked box in jp and dload via ssh ?
asciilifeform: it dun come for phree with the pipe, round here
asciilifeform: ( symmetric to/from uy, jp, etc, rather than to lolcat local cache, i dun subscribe to the latter )
asciilifeform: BingoBoingo: interestingly, the cache-of-lolcats thing actually seems to have freed up substantial bw for actual net traffic. to the point that my 100bux actually buys symmetric 100mb/s here, on erry day of the year except when some idjit backhoes the fiber
asciilifeform: i.e. could build router that simply... routes. rather than trying to be 'smart' and keep stateful connections.
asciilifeform: fwiw simply rejecting tcp won't do the trick, you also gotta not allocate state for udp ( all extant routers, afaik, do.. but e.g. s.mg protocol and similar, will operate entirely correctly without this, as i understand it )
asciilifeform: ( and also happen to know why : they 'give to allcomers' in the sense of allocating memory for state of tcp connection. therefore it stands to reason that if one built router that doesn't tcp at all -- it will not fall. )
asciilifeform: granted i know that they ~do~ fall down, but to me this suggests that they're made of wadded toilet paper, rather than it being an inescapable physical fact
asciilifeform: briefly upstack to http://btcbase.org/log/2019-01-22#1889021 << possibly i'm thick, but it ~also~ never made sense to me why a ~router~ would fall down, either. seems like if yer pipe is e.g. 100mb/s , and incoming enemy crapola at 1000mb/s, then you simply oughta get (from pov of arbitrary test peer) 90% packet loss. rather than a smoking crater where router was.☝︎☟︎
asciilifeform: BingoBoingo: subj aint a short-term urgent itch by any means. moar re general principle
asciilifeform: that way you can have something like civilized engineering calculation, rather than ' i dun know if i'll buy 3 kg of potato or 4, so let me bring a 50 tonne flatbed truck'
asciilifeform: assertion is, the cost of a processing job oughta 1) be calculable in advance of performing said job 2) depend only on ~said job~, rather than what else the machine happened to have done recently or may be doing concurrently with remaining cycles
asciilifeform: BingoBoingo: the pt i was trying to make is possibly too subtle to readily make sense until i write a proggy around it, to illustrate. which sadly aint happening in near term.
asciilifeform: BingoBoingo: last i recall it was =~ apache, but with buncha features cut out ( phpism, load balanceism, etc )
asciilifeform: BingoBoingo: apache afaik is hands down best horse in that glue factory.
asciilifeform: BingoBoingo: they're all exactly same from this pov
asciilifeform: sorta like, building bridge of solid rock all the way from road to sea floor is great, if you have infinite rock, but is titanic waste, if yer at all interested in max bang for yer cement bux
asciilifeform: it doesn't stop being retarded simply cuz mircea_popescu and for that matter asciilifeform give the thing 256GB of ram to run it and never see the barf☟︎
asciilifeform: this is well studied in trb, but applies elsewhere
asciilifeform: mircea_popescu: my objection is to the prng element in apache and other heapistic proggies, where actual resource consumption is a function not only of req rate, but how much footprint of each one happened to be , fragging the heap
asciilifeform: i'll believe, will assume mircea_popescu actually tested with a lan-connected box requesting loads at gb/s or whichever. but to make this guarantee with apache and other heapistic softs, needs massive margin of iron
asciilifeform: mircea_popescu: a sane server oughta work at ~line~ rate
asciilifeform: if architecture of bldgs worked the way apache is worked, all structures would be pyramid
asciilifeform: not dead, but couldja say just how many cycles/s and bytes of ram will give what # of loads/s ?
asciilifeform: and ( again like trb ) it dies disgracefully at the boundary of capacity,
asciilifeform: mircea_popescu: thing is roughly like trb - can throw iron at it until it eats the desired reqs/sec without shitting self. but, just as in trb, it's a barbaric/empirical ritual, quite impossible to say 'on napkin' how much cpu will yield what # of what kB pg served /sec w.out falling
asciilifeform: mircea_popescu: the microshit people, innocent of opensores, did same, it's a c macula
asciilifeform: ( at the risk of pedantry : they used ~heapism~ . consequently, found it impossible to answer the q 'does machine have the cycles to do this-here request?' in o(1) ! )
asciilifeform: the folx who shat out apache & co., i suspect were at least as aggressively retarded as koch.
asciilifeform: if the cycles aint there to serve a page or whatever op, then simply shouldnt ACK, that's it
asciilifeform: why the fuck should it ever fall down.
asciilifeform: incidentally, imho it's rather perverse that the popularly expected behaviour in 'moar server reqs / sec. than can be serviced' is 'fall down' rather than 'triage + busy signal'
asciilifeform: in other lulz, 'numpy' ( 1 of the few useful libs for that lang, does various numericalmethods ) Officially turns tard, proclaims 'this is last ver to support python 2.7, from nao on 3'
asciilifeform: depressing subj, back when i had crt, never 1ce saw 'frame tear', not since cga days at any rate
asciilifeform: ( this is ~already~ a metre or whatever - sized sram ! )
asciilifeform: ( which , if lcd, is ~regardless~ stuck latching the bits, even nao )
asciilifeform: iirc we even had a 2014 thread, whole thing where machine shits the frame to the lcd at N hz, is retarded, framebuffer oughta live in the display
asciilifeform: funnily enuff, even the 60hz panels are 'step back' in that they have sloppy vsync, frames tear.
asciilifeform: in the http://btcbase.org/log/2019-01-21#1888701 days, that crt was already the last 1 in the lab ( the headpiece was a lcd shutter, and demanded a 120hz display to output the left-right sequential frames. so had to crt. )☝︎
asciilifeform: re eulora -- occurred to asciilifeform to wonder, does the thing actually demand the 3d card ? or could just as readily polygonize with cpu
asciilifeform: babbage 'жил, жив, будет жить', a la lenin.
asciilifeform: there's oddballs continuing the 'fine tradition' out of , i suspect, sheer nostalgia. ( i do not know whether they use clothespin or get somebody to break nose tho... )
asciilifeform: y'know, same fella who turned 'diehard' into 'умри тяжело'
asciilifeform: btw apparently the 'translator wears clothespin on nose' item is mythical : turns out that good % of the tapes were simply dubbed by this 1 ex-boxer, with perma-broken nose
asciilifeform: mircea_popescu: we had such 'dubs' that one still could ( and normally would, if actually care to understand half a shit ) hear the orig track
