Increasing latency can also reduce TCP throughput ceiling, increase in-flight concurrency, and increase server memory consumption.
HN user
dumah
Wire protocol applies to external interaction with the db.
Internal ABI/API is used by extensions to directly interact with core subsystems and depends on internal models for things like storage.
It might be analogous to HTTP versus an nginx plugin.
Of course market participants agree?
Exchanges have calculation rules for every type of mark and payment and will always specify rounding.
Paris would need significant infrastructure work across the distribution system to handle AC at NYC’s rate of 90% on summer heat wave days.
Sure he does.
It's not handwaving to complain that shipped features are never completed and a functional CLI for fundamental and critical tasks is never delivered.
The same way you get value out of a dev container.
Regulators don’t want to provide arbitrarily detail into their interpretation or likely judgements on issues that may come up for many reasons, good and bad.
One good one is that providing concrete razors for compliant and non-compliant behavior accelerates the gaming of the rules.
How are resource and territorial pressures not environmental pressures?
If you take Pliny’s word for truth, they did achieve 10% of the scale of the largest currently operating gold mine using hydraulics at Las Medulas.
Modern geological estimates are radically lower.
so why throw away all that time?
Tack is short for tackline, a length of line used to delimit messages encoded with flags in the days before shipboard radio communications.
Military and civil emergency communications use alternative pronunciations where clarity and brevity are critical.
This is one of the most sustained bad-faith arguments I’ve seen on HN.
The idea that 4 of the largest investment banks in the US were destroyed is not just utterly false, it’s hard to imagine how one could interpret the outcome in this manner.
Why would anyone be happy that the government offered handouts that were stolen, low-level criminals prosecuted, meanwhile every single principal who was culpable went unpunished?
I don’t need to hear from you how this is off-base or I’m misunderstanding. I’m close to principals involved in the crisis and worked for years in the response to it, and have heard what went on in the meetings dramatized afterwards.
These companies innovate in all of those areas and direct those resources towards building hyper-scale custom infrastructure, including CPU, TPU, GPU, and custom networking hardware for the largest cloud systems, and conduct research and development on new compilers and operating system components to exploit them.
They're building it for themselves and employ world-class experts across the entire stack.
How can NVIDIA develop "more integrated" solutions when they are primarily building for these companies, as well as many others?
Examples of these companies doing things you mention as being somehow unique to or characteristic of NVIDIA:
Complex kernel drivers or modules:
- AWS: Nitro, ENA/EFA, Firecracker, NKI, bottlerocket
- Google: gasket/apex, gve, binder
- Meta: Katran, bpfilter, cgroup2, oomd, btrfs
Hardware simulators:
- AWS: Neuron, Annapurna builds simulations for nitro, graviton, inferentia and validates aws instances built for EDA services
- Google: Goldfish, Ranchu, Cuttlefish
- Meta: Arcadia, MTIA, CFD for thermal management
Optimizing Compilers:
- Amazon: NNVM, Neo-AI
- Google: MLIR, XLA, IREE
- Meta: Glow, Triton, LLM Compiler
Acceleration Libraries:
- Amazon: NeuronX, aws-ofi-nccl
- Google: Jax, TF
- Meta: FBGEMM, QNNPACK
You're generalizing a failure at delivering one consumer solution and ignoring the successful infrastructure research and development that occurs behind the scenes.
Meta builds hardware from chip to cluster to datacenter scale, and drives research into simulation at every scale, all the way to CFD simulation of datacenter thermal management.
performance degradation observed using the first approach at high concurrency recently discussed here: https://news.ycombinator.com/item?id=44490510
This conception is simplistic, a straw man, and one that appears to be wholly ignorant of the Cosmopolitan tradition and reasonable criticisms thereof.
What a fallacy to equate the status quo of lawyers running the country with the United States itself.
No, on the balance it is lawyers who protect companies from the people they harm and lawyers who constitute the government officials who perpetually exceed and expand their mandates.
Most of the senate are lawyers and it’s the most frequent occupation of a legislator.
That’s irrelevant to the fact that the expected PnL on a millisecond of latency improvement is a lot more than 1M in some markets. Obviously if you are getting what ever trade you are concerned with off in less than one millisecond, the question isn’t well posed.
There are many more games to play than delta one takeout and the solutions certainly don’t fit on one or a handful of FPGA’s.
They don’t charge fees, because they’re not a brokerage or exchange.
They pay fees to exchanges.
As a market maker, some rebates are given back conditional on their activity.
They have no users.
You’re just constantly obliviously asserting falsehoods that betray an almost comical lack of understanding of the reality of these businesses.
You have no concept of the infrastructure and organization necessary to operate these enterprises.
All your posts here are low-information anti-finance rants.
There’s tons of latency sensitive code outside of the FPGA systems and it is not simple.
No, there are absolutely electronic trading markets where a difference of milliseconds of latency to certain events is worth more than a M PnL. That’s a long time.
You can fingerprint transmitters.
Antennas would be much more difficult and likely moot.
Only a few percent of Down’s syndrome cases result from Robertson translocations and may be inherited.
If the mother carries the translocation, the rate of recurrence isn’t much more than 10%. If it’s the father, it’s significantly less.
Fantastic post.
Please do one on your analysis and optimization workflow and tooling!
I’m not sure why you’re comparing __new__ to constructors in other languages.
Ruby has the same thing but it’s called ‘new’.
Implementing the type of customization (idiomatically) that __new__ provides in Kotlin and JS isn’t any cleaner.
That’s not “the normal way”, it’s just the case when the LHS is immutable.
This behavior is congruent to C++ and it’s documented and idiomatic.
It’d be weird if the in-place operator deeply copied the LHS, and problematic for a garbage-collected language in high throughput applications.