1,672 karma · joined December 5, 2014
hnchat:iah9cGDqdgU2TCHEINZt
Does it mean Gosset stop before the distribution converging to normal distribution?
Is it correct to say memory behaviour of a program entirely depends on what/how the program allocates and its memory access pattern? Is there any hello world memory allocator out there?
File system moves blocks to memory, and kernel access them as pages, and kernel also moves them back to disk(using file system) depending on memory pressure. Given this is ture, I am assuming, when studying memory behaviour, virtual memory setup is good enough to ignore file system level details initially - but at what point these details become important? For example, just as cache miss, I am assuming, it is also very expensive for file system(paired with underlying physical medium) to go out and gather non-contiguous blocks and put them together to respond to a file access request.
Does it mean radio is using portion of this 10mW? If so, how much?
This is very interesting. Can you share more about this?
Link[1] was referring as a solution to this problem in this article: Absolute Minimum Every Software Developer Must Know About Unicode in 2023 [2].
[1] https://www.unicode.org/reports/tr29/#Grapheme_Cluster_Bound...
Does each interaction essentially create a SQL update statement? And are you trying to avoid buffering those statements?
Choosing next input based on present sounds a lot like a Markov chain - is that something you guys use when simulating user interaction with distributed system?
How much of the process can be pushed to server side? (Sorry, I don't speak JS.)
Source: https://github.com/urllib3/urllib3/releases/tag/2.2.0
Type: Cloud Computer - Shared CPU
Location: New York
OS: Debian
Plan: Regular Cloud Compute
Auto backup: Disable
No doubt, they will make it even harder to find in the future - behind some new feature toggle.
[1] Spoke with @LisaSu. She was very polite, but said nothing of substance and indirectly rejected my offer.
Here’s a firmware crash, run ./loop.sh to trigger. Tested on tinybox and 1x7900XTX machine, ROCm 6.0.2 and 6.0.3 preview. Must reboot to bring back.
[2] No need to hire me, just open source the 7900XTX firmware+docs and remove the signature check. We'd treat it like bring up for our own chip, get builds in CI, HITL testing, fuzzing, etc...
Deadline, end of the week? Otherwise I'm not spending more time thinking about this.
Source https://twitter.com/realGeorgeHotz/status/177166635165378186...