mtanski

105 ms·

331.
by mtanski 11y ago
I think you just kind of proved my point that real work load benchmarks would have to be much more attractive to offset the cost of supporting an architecture that's not tier one in many languages / software libraries / proje
332.
by mtanski 11y ago
The spark workflow is 10% cheaper (24.36 vs 21.88) over 3 years. Is that really worth having to support a non-mainstream architecture? I doubt it.
333.
by mtanski 11y ago
And you had all the great amenities that you cannot get in Manhattan like the Casino and the Race track not far off.
334.
by mtanski 11y ago
Since we only have two parties, each one doesn't want to do anything in the odd case it would give the other one an edge they don't know about. So things stay shitty.
335.
by mtanski 11y ago
Pretty sure that's not how diplomacy works. There's a pretty good podcast on Planet Money how things are negotiated in trade deals.
336.
by mtanski 11y ago
> And all they really do is show that you should have money and the real problems aren't the drugs but finances and society. I think many socio-economists would agree with that statement.
337.
by mtanski 11y ago
Pretty much all these distributed databases at their core somehow handle the partitioning of data. Even if sometimes it's just throwing up your hands and saying there's a user has to provide us a partitioning function. That's
338.
by mtanski 11y ago
Fist of, this looks like a fun project. I haven't seen the implementation but it looks they built the new database using the current state of the art from db / data structure literature (distributed b+ trees). On a semi-unrelated
339.
by mtanski 11y ago
The async story on windows is better, but not great. In many cases the async calls on windows silently block due to a number of special cases (that are not so special).
340.
by mtanski 11y ago
I think a lot of folks think of Network IO when they say Asynchronous IO. That's only half the story, unless you're just building proxies and caches you have to deal with Disk IO at some point in time. And, async disk IO is horrib
341.
by mtanski 11y ago
Obviously, bandwidth is not the same as latency. GPUs cards makers the trade of between bandwidth and latency i n favor of latency. When you're doing mostly branch free processing in large chunks that's the trade of to make. All y
342.
by mtanski 11y ago
Current gen GPUs use GDDR5 compared to DDR4 in only handful of new Intel chips that started shipping in the last few weeks. The GDDR4 chips runs at 750Mhz and DDR4-2133 as supported by the fasted shipping Intel CPU runs at 266Mhz. That is a
343.
by mtanski 11y ago
GPU and CPU cores are very different in how they process data / architecture. You can think of GPU cores as you schedule a series of "vector" instruction over a large chunk of data. They are great at internally paralleling th
344.
by mtanski 11y ago
ext4 is really good at the single user (single process / single thread) use case. Other file systems shine in different categories like number of features (btrfs) snapshots (btrfs) very large devices (xfs) really high concurrency (xfs)
345.
by mtanski 11y ago
Games for a long time struggled to with scaling up to more then one core. Even today the games scale to like 2 or 4 cores. Just at the PS3 cell, it took a long time for games to really utilize the PS3's full potential. That's why
346.
by mtanski 11y ago
The expected behavior for C++ destructors is pretty well documented. Eg. don't throw in a destructor / don't do things that would throw in a destructor. You're free to try to skirt these rules, but if you get caught that
347.
by mtanski 11y ago
While I think this is an important problem to solve, it's not lost on me that this isn't an easy problem to solve. It's complicated further by design decisions like no stack unwinding and current behavior. I'm not sure t
348.
by mtanski 11y ago
Rust's goals are both type and memory safety. I consider an OOM with a panic/abort a memory safety issues. Linux also does these kinds of things to your process, but there at least you can opt out of it. I agree with you, in the r
349.
by mtanski 11y ago
C libraries are worse, esp. the desktop focused ones (glib and all of gnome). Network focused libraries tend to be better (lib libevent / libev), and you see people send patches to fix OOM cases since enough people disable over commit
350.
by mtanski 11y ago
> No one would (should!) ever consider writing a webservice in C++, simply because it's unsafe to do so That's a pretty bold statements. By the same account, you should not write a webservice in rust because it's unsafe. O
351.
by mtanski 11y ago
Same here, the borrow checker in it's current incarnation left a sour taste in my mouth. What made it worse, the language market keeps plugging the borrow checker as this great fully baked feature. And (like you said) in real life it&#
352.
by mtanski 11y ago
Yes, a shady car service that in many cases does not have a price before hand, that does not take credit cards, that always tells you it will be there in 5 minutes (even if you'll be waiting 30+ minutes).
353.
by mtanski 11y ago
This seams like the best practical way to schedule garbage collection next to tracking the users eye movements (joke from the Go lang presentation about 1.5 GC). In all seriousness: since the environment is pretty well controlled compared t
354.
by mtanski 11y ago
Consumers don't care.
355.
by mtanski 11y ago
I made the mistake of reading the comments on this NYT article. The thread is filled with people who are against recycling at collections points. This has been one of my pet peeves for a while now. We should be figuring out how stop delegat
356.
by mtanski 11y ago
Everything immutable (every data structure) is a really convenient way of thinking about processing data in the abstract sense. You can think about processing your (semi) structure data (records) in terms of high level pipelines and process
357.
by mtanski 11y ago
My buddy Adam put this together for Cassandra. It's always nice seeing somebody do this kind of work and share it publicly. We do similar kind of benchmarking ourselves for our applications between cloud vendors and instance types (dif
358.
Comparing Cassandra Write Performance on Google Compute Engine and AWS(blog.cloud-benchmarks.org)
29 points by mtanski 11y ago|3 comments
359.
by mtanski 11y ago
You could randomly spread this over various subs, that and add erasure coding. This way if a chunk or two goes missing you can reconstruct the original blob.
360.
by mtanski 11y ago
He is like the John Stuart of Fin reporting.

More ›