Recent submissions

Comment · 4 years ago
This might be an error on both sides.

They want to study how websites handle GDPR and CCPA, and that's probably what they submitted.

The IRB reasoned that "websites are not people", which is true, but failed to reason that "websites are operated by people", and therefore certain measures should be taken.

The IRB bears some responsibility for this.

Comment · 4 years ago
A simple way to do this is to:

MyNestedMaxHeap(T, Ord) = MaxHeap(MaxHeap(T, Ord), Ord)

such that when using MyNestedMaxHeap only one Ord type can be passed.

Comment · 4 years ago
> You need some way to enforce that the orderings are the _same_

Just require that the Ord type is the same for all heaps ?

MaxHeap(MaxHeap(T, MyOrd), MyOrd) uses the same ordering, but MaxHeap(MaxHeap(T, Ord0), Ord1) does not.

Comment · 4 years ago
> If you didn't have canonical implementations, you would have to give up being able to write safe & efficient data-structures like this.

No? Just make the type generic on the ordering.

Instead of MaxHeap(T), make it MaxHeap(T, Ord:(T,T)->bool) or something like that.

Comment · 4 years ago
I agree with you, which is why I don't really understand what the point of improving FP64 perf by 4x is, if that is not the bottleneck for many apps.

Per node, a 4x MI250X node has more or less the same BW as a DGX-A100 (8x A100). It has 2x more FP64 compute, but for most science and engineering apps, which are memory bound, 2x more FP64 compute does not make these apps any faster.

Comment · 4 years ago
Makes sense. Comparing nodes with 2x or 4x MI250X vs 4x or 8x A100-80 it doesn't really seem that there is any speed up at all for memory bound apps.
Comment · 4 years ago
Then you must be extremely bad at rust.
Comment · 4 years ago
Many in the core team don’t code, don’t even know Rust well, etc.
Comment · 4 years ago
I wonder how they manage to keep the FP64 units busy. Seems this is an HPC product, but many HPC apps are memory bound. So to improve FP64 perf by 4 one might need to improve DRAM bandwidth by 8-16x. Otherwise the units would only be stalled waiting for memory.

But it seems they did not improve bandwidth by much?

Comment · 4 years ago
Ideally it would be a constitutional ammendent, stating that privacy is a right of every citizen, and a human right.

Legislation to the right to encryption would then just follow from it, but having it in the constitution would make it harder for future governments to pass certain kinds of legislation, or if they pass them, the supreme court would declare them inconstitutional.

Comment · 4 years ago
Its not completely unrelated.

Excess mortality is the only fact that we know for sure given that every country counts "COVID deaths" differently.

Given that there is a statistical difference, the only thing we can probably know for sure is that an individual chances were slightly better in the EU.

The difference is small, like others have mentioned, so it doesn't seem like EU policies did a lot for the whole EU.

This makes sense, since for example Germany had pretty harsh policies, but due some of its neighboring countries having pretty lax policies (e.g. Austria), some parts of Germany were extremely affected (e.g. Bavaria).

This hints that it doesn't really matter if single states have harsher policies as long as neighboring states do not, at least for states of the size of Germany.

If we look at China, which had a very cohesive policy in all its provinces, the story differs.

This hints that if cohesive policies would have been taken at EU and USA scale, the outcome might have been different.

That didn't happen, so we will never know for sure.

This doesn't answer the OP question, but if someone claims to have an answer, they are probably lying, because we don't really have facts to back that answer up.

Comment · 4 years ago
Right, but all architectures can handle many combinations of instructions in 1 cycle, so this is not really a great proxy for that.

Same for code size. If the instructions are half the size, having 1.5x more instructions still means smaller binaries.

Comment · 4 years ago
8x 2 byte instructions (16 bytes) lead to smaller code than 4x 8 byte instructions (32 bytes).

Counting number of instructions isn't really a good metric for that either.

Comment · 4 years ago
> DPU SmartNICs,

Which other companies beyond NVIDIA sell DPUs ?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton