puzzle

9 ms·

31.
by puzzle 8y ago
There was also a talk about the low level storage service and the performance isolation work that allows it to mix batch and latency-sensitive traffic on the same drive, but it doesn't seem to have been recorded: http://www.
32.
by puzzle 8y ago
It looks like a lower tier than the existing Coldline and Nearline (7x cheaper for storage than the former). Both have a minimum period, so this one is likely to have one as well. Coldline and Nearline are more expensive than regular storag
33.
by puzzle 8y ago
"Fast" is relative here. It's fast compared to Glacier and others, but it's going to be slower than the more expensive tiers. You might not need to speculate much about how it works, it's probably implemented as des
34.
by puzzle 8y ago
Kind of. It's only the traffic management part, i.e. the external load balancer. It seems to be a mix of a managed Istio Pilot plus a bunch of stuff from GCLB: anycast, backend subsetting (Envoy does not do the health checking), etc. T
35.
by puzzle 8y ago
I am pretty sure that was developed for Monarch. Perhaps later it was adopted by BM to consolidate storage, but still through a dumb API? I know that originally it had a bunch of files in GFS, with a layer of indirection, because there was
36.
by puzzle 8y ago
No, I think it's strictly about where aggregations and other computations occur. You hint at that when you mention CSV files. Borgmon keeps X hours of data in memory and looks up anything older from TSDB. I never understood how to aggr
37.
by puzzle 8y ago
Ceph?
38.
by puzzle 8y ago
I miss TBR=. You should rarely use it, by design, but in those few occasions where it's warranted, it's very nice.
39.
by puzzle 8y ago
The actual proverb, by an engineer (Paul C), is "there are two ways of doing things at Google: the deprecated one, and the one that doesn't work yet". Usually the deprecation occurred when a service outlived the original requ
40.
by puzzle 8y ago
For many years there was also a wiki that just didn't refuse to die. I think that when I left there was yet another attempt going on to migrate the content away from it. Surprisingly, one of the main appeals was that its availability w
41.
by puzzle 8y ago
If C++ is an option, Baidu has a clone called Tera.
42.
by puzzle 8y ago
Yeah, HDFS is a toy in comparison. It's barely comparable to the original GFS, which was retired... Almost a decade ago?
43.
by puzzle 8y ago
I remember Larry saying that in reality for a long time the homepage was spare because Sergey's HTML sucked (or vice versa). I worked on a project that fell under her umbrella. I have seen up close some of the things she gets blamed fo
44.
by puzzle 8y ago
It's worse than that: the German press pretty much runs the show.
45.
by puzzle 8y ago
Does anyone outside the company know how DDG works? IIRC a job description hinted at their backend being in Perl, but little else has trickled out. It's easier to find out how Google works, through patents, presentations, the Percolato
46.
by puzzle 8y ago
That's kind of how Google works, with multiple index tiers. Look up patents by Anna Paterson to get a few clues, assuming your lawyers won't bark at you. Still, you can't keep partial results around forever, unless you want t
47.
by puzzle 8y ago
Behind the scenes, a search on Google involves at least a thousand machines. How much extra state (internal connections, memory for partial results, etc.) would such a new search type create? How do you deal with a new kind of hot spots now
48.
by puzzle 8y ago
How current is that page? Yahoo used Google since 2015.
49.
by puzzle 8y ago
Interview questions: How would a search engine distinguish between the two kinds of queries, tens of thousands of times a second? And how would one architect such a two-tiered system, particularly with an eye toward cascading failures?
50.
by puzzle 8y ago
Google's index has been in memory for most of its life now: http://glinden.blogspot.com/2009/02/jeff-dean-keynote-at-wsd... It's actually more complicated than just a single static index, which is also w
51.
by puzzle 8y ago
The Amiga had 880KB (DD) or 1760KB (HD, with a special drive) floppies, but instead of increasing track count, it had more sectors (11) in each of the 80 tracks.
52.
by puzzle 8y ago
As with most coding questions, the important parts are when you start looking at corner or edge cases. Or when you refine your initial implementation.
53.
by puzzle 8y ago
The site says it compiles to bytecode and C++ source. Looking at recent commits, there's some non-functional WASM support: https://github.com/aardappel/lobster/commit/5b89bacd1b1d1e63...
54.
by puzzle 8y ago
It's already the minimum in NYC starting this year.
55.
by puzzle 8y ago
Sony had probably the most stylish designs among MSX manufacturers. They were not afraid of using curves compared to e.g. Philips' boxier style. There was some other interesting stuff in the 80s, like the systems from Apricot (formerly
56.
by puzzle 8y ago
According to someone that worked on Blogger, a decade ago one of the top three or five sites in all of Greece was this blog, Troktiko, which tragically went into hibernation when the cofounder, a journalist, was murdered.
57.
by puzzle 8y ago
That's a good question, but I have a hunch and am willing to bet that by sheer coincidence they will focus particularly on the smallest of the seven named.
58.
by puzzle 8y ago
The A590 had both a SCSI and an XT header for internal drives (on the right side): http://amiga.resource.cx/photos/photos/a590-5.jpg I only ever saw them with SCSI drives in person, but they also sold XT units. Ma
59.
by puzzle 8y ago
The A590 was a drive that plugged on the left side of the A500. It usually came with a 20MB SCSI disk inside... There was no room in the A500 for a 3.5" drive. Later, the A1200 and A600 had a built-in IDE controller and an internal bay
60.
by puzzle 8y ago
It might have been a SCSI drive/controller, but it might have also been that you used FastFileSystem, which was pretty efficient. One of the HD manufacturers of the time, either Conner or Maxtor, was known to use Amiga 3000 machines to

More ›