fitshipit

no, it doesn't. loose isn't a verb. loosen is

UpThere?

Erdös started taking benzedrine in 1971, long after he had become one of the most prolific mathematicians of all time with ~40 years of work behind him. I suspect he was productive in spite of the speed, as someone that brilliant with that many years of learning in their head would still be incredibly brilliant impaired.

I would love to see this at hackathons and conferences everywhere. So many people need help but are so ashamed to ask for it (particularly in our field) that you literally need to make talking to someone as convenient as getting a McDonald's hamburger to get them to seek help.

Sounds like the opposite of what you'd want in building a business.

It depends completely on the application. It's also usually best to focus on the tail end -- I've always found alerts on 95th or 99th percentile latency useful and easy to decide on thresholds for (ask yourself -- how slow can I tolerate this being for 1% or 5% of users?)

> Know Paxos? Stealth-mode big data startup is hiring founding engineer

lol

Red Hat? Or what about Facebook or Google -- open source is pretty central to their business model.

This piece is in fact even more speculative than the FBI's announcement.

This reminds me a little of the Netezza data warehouse appliance's architecture: a query planner in front of lots of little nodes with one disk, one CPU, and an FPGA. Every query is a full table scan, each node flashes the WHERE clause to the FPGA, and slurps the whole disk through the FPGA.

Yes, but each of those cores does very little compared to one core on a CPU.

in some cases the checksums are persisted, so future checksums must be computed in the same way.

parent is referring to a multithreaded algorithm, not one that uses SIMD instructions, which is what is meant by vectorizing.

I believe based on context that you and the article are talking about different kinds of parallelism. Yours is the more usual sense, the author seems to be referring to the fact that CRC does not exhibit instruction level parallelism which out-of-order execution exploits. This is because the loop is very tight (probably a few instructions) and each iteration depends on the results of the previous, so there is only a tiny window for reordering instructions.