The existence of a kill switch plus tracking in legislation very likely means the manufacturers wanted to track and sell user data and needed a scapegoat to avoid customer backlash. I would profoundly surprised if we don't find a lobbyist at the bottom of this.
I have not read the books, so I guess I'm the target audience. It was very hard to watch. The actors were fine, actually better than fine, but the writing was painful. There are lots of standard adventure and fantasy arcs that are just impossible to carry forward with the type of "modern" they wanted. For instance, you cannot have the most diverse village in the history of villages anywhere, then later the Orc (?) stares at one of the kids once and goes "you are not from this village, you are certainly from this other village because of how you look". How? Aura color? At least change it so the kid has a tattoo or some birth mark then. I could go down a long list of dumb stuff like this that makes me come back to reality instead of allowing me to stay with the flow and enjoy the fantasy.
I reread the books multiple times. I was actually pretty impressed with how well they cast each character. Which is impressive because I think that's one of the hardest things to do.
But, the dialogue and storytelling were terrible. They invented new, pointless content. There's ~18k pages of source material. Amazon's job was to figure out how the hell to pair that down without compromising the original story. Instead, they went for visuals over storytelling
There’s actually an in book way to explain that, the clothing is always described as specific to the two rivers, and only Aiel have red hair. I agree The show was awful!
I don’t think that the ethnicity of the actors really matters all that much, the height & hair color are the only real trait that describes how Rand stands out. Honestly the only character with a skin color description I can recall is Tuon? And that isn’t really something that matters either…
Bigger issues as other people pointed out are things like inventing weird bullshit storylines when you have 10k pages of content to draw from, or messing with the “hard rules” of the magic system, such as you can’t burn out in a circle, or heal someone from death.
It ruined the suspension of disbelief immediately for me though. A rural village that doesn’t do constant international trade should have people living there that all look, speak, dress, and act similarly.
But the village looked like like an HR training video. To contrast, a new season of squid game just came out. Everyone is Korean. Everyone speaks Korean. Everyone looks Korean.
Right, the characters skin tones and real life ethnicities ruined the suspension of disbelief, because that’s harder to explain than Trollocs and the One Power??? Or Fades? Or the Dark One?
Or maybe you are hyper focused on specific, racial, details that you care about due to some internal biases?
Calling failing to show up or nominate a legal representative to a judicial hearing in a country that offers a ridiculous number of opportunities to appeal as "feud" shows some bias in reporting.
You. don't. say. Really?!? OMG, what an insight! What are they going to say next? That startups also use the good will of the internet to create their IP to then take it private as a way to get free labor? I'm shocked! And because this is also the internet, that was sarcasm.
Allegedly Costco has a policy of making their white collar folks work on the floor of their stores and rotate positions before getting to the office, same with McDonalds. I would love to hear from someone with first hand experience to confirm or correct my impression. I did confirm that Costco gives good benefits and decent pay for all their automotive section employees, and since then I only buy tires there (since 2000) for that very reason. Every time I visit I reconfirm that is the case. It is not much in the great scheme of things, but it is an honest effort to buy from good employers.
I wrote last year's benchmark. The clusters are completely different, and so is the workload.
Last year's cluster had 300 VMs, which was a much higher price point, and the workload was write only.
This benchmark uses YCSB workloads A and B, which we though matches the usage we'll have on BigTable. The cluster is much smaller as well.
I shared my scripts from last year, it is pretty easy (although a bit expensive) to repro the numbers. Let me check if we can share this year's benchmark scripts as well.
I'm pretty surprised about the difference in latency though, throughput as you say will be different due to number of nodes.
For any given replication factor in Cassandra, overhead remains the pretty much the same irrespective of whether you have 300 or 3 nodes. So should the latency.
On top of that both BigTable and Cassandra use SSTables to store the data on disk (with all the compactiony goodness that goes with them), so I'm even more surprised that the difference in latency is so huge.
Would love to see the scripts for the benchmarks! I don't want to take away from a great product launch and I'm sure BigTable kicks arse in certain areas that Cassandra doesn't... I'm just surprised at the differences in latency.
Hi,
The cost we published includes the time to setup the whole cluster, warm up the data nodes, and run for 5 minutes at 1M per second.
Our run rate is $281 per hour, which is the same as AWS a couple of years back. What changed is that we are using quorum commit, the data is encrypted at rest, we have very low tail latency, and we look at all samples when computing that.
Computing our price is easier because we do not charge per access.
Here is the formula for our run rate:
30 loaders (n1-highcpu-8) at $0.522 per hour: 248.7
300 nodes (n1-standard-8) at $0.829 per hour: 15.66
300 1TB PDs that run at 0.055555556/hour: 16.67
Total: 281.03
I wrote the test - Yep. Tail latency is one of the key things here. And I took 100% of all samples, as opposed to the middle 80% the tool usually reports.
Network average utilization was low by design. Keeping it steady was more important than low, though, and harder too.
Latency spikes come from Cassandra flushing data to disk (large sequential IO), Java garbage collection and heap resize, and page faults during compactions (random reads).
What I did to even traffic out was to enable trickle_fsync and size the flushes, set Java's max and min heap sizes, as well as to tune the Java heap ergonomics. I treated random reads as a fact of life - I did nothing to tune that.
Doesn't GCE run on the same (physical, not logical) network as the rest of Google's production systems? If so, which I believe is the case, how can you control for network utilization?
