skysight-inc/HackerNews huggingface dataset:
Getting full throughput from the SSD is less about file size and more about how much work is in the SSD's queue at any given moment. If the host system only issues commands one at a time (as would often result from using synchronous IO APIs), then the SSD will experience some idle time between finishing one command and receiving the next from the host system. If the host ensures there are 2+ commands in the SSD's queue, it won't have that idle time.

Then there's the matter of how much data is in the queue, rather than how many commands are queued. Imagine a 4 TB SSD using 512Gbit TLC dies, and an 8-channel controller. That's 64 dies with 2 or 4 planes per die. A single page is 16kB for current NAND, so we need 2 or 4 MB of data to write if we want to light up the whole drive at once, and that much again waiting in the queue to ensure the drive can begin the next write as soon as the first batch completes. But you can often hit a bottleneck elsewhere (either the PCIe link, or the channels between the controller and NAND) before you have every plane of every die 100% busy.

If you're working with small files, then your filesystem will be producing several small IOs for each chunk of file contents you read or write from the application layer, and many of those small metadata/fs IOs will be in the critical path, blocking your data IOs. So even though you can absolutely hit speeds in excess of 3 GB/s by issuing 2MB write commands one at a time to a suitably high-end SSD, you may have more difficulty hitting 3 GB/s by writing 2MB files one at a time.
I agree that distorting focus is often a propaganda tool and diversionary tactic, but it goes both ways. Sometimes the category of problem really is larger and more widespread than the single cited instance, and it’s necessary and reasonable to see the forest rather than just the tree, particularly when the best solution applies to the forest as a whole; e.g. to close the widely exploited loopholes.
> Regarding your performance work, you've nerd sniped me into looking for analytical tricks to speed it up ;) We'll see...

Looking forward to it! These microbenchmarks are very fun to explore.

> Side note: any idea why the python and fortran are exp(i k... while the julia is exp((100 +i) i...)? Is it something I overlooked?

Oh, that is a partially applied edit I guess. When the author posted on the julia forum, people pointed out that since the exponent was pure imaginary, it could be speeded up even more with cis(...) instead of exp(im * ...) but then the author claimed that exp((100 + im) * ...) was more representative of his actual workflow and I guess changed the julia version in his blogpost but not the Python or Fortran versions.
You voiced your comment as more speculative rather than as a question. Please don’t stop asking questions!
It won’t do anything.

Also, Carrington class events are very rare. You should worry more about space junk crashing into important things and even then it’s not much of a worry.

https://warwick.ac.uk/newsandevents/pressreleases/likelihood...
It looks interesting, but how does it behave with dynamically created queries?
first ting I thought of was The IT Crowd: https://www.youtube.com/watch?v=iDbyYGrswtg
If it manage to do a gravity assist maneuver around some existing planet, it might. Probability of such is very low, I believe. Moreover, I think if there was any chance, scientists already knew about it. If they keep silence, then no, there are no chances.
Carrying groceries 10 blocks in NYC isn't the easiest thing. This would help.

But if you live in car dominated sprawl then idk.
The visual effects industry is structured around a bidding process that cements VFX studio compensation before film production has begun. However, film is a collaborative medium with financial and production risks with decisions often pushed to a later date "to be solved in post". That post production VFX stage has grown in size, grown in the types of production solutions provided, all without additions or modifications of compensation. They simple get to keep the ongoing contract, regardless if doing so bankrupts the VFX studio. Which it often does. The production digital artists receive their contractual compensation, they get to keep their jobs, but the production becomes 14 hour days, 6.5 days a week for 6 to 9 months. Meanwhile, this is taking place on all 6-12 productions flowing though the VFX studio at the same time. At some unknown time, the bank and investors simple say "no more" and the studio implodes. This is the concrete reality of the VFX industry. This is how people do not get paid.
Welcome to the land that no country wants (2016)
If you're not otherwise covered, I think it makes sense to accept their liability insurance, since that could involve significant sums. But yes, most should decline damage waivers etc.
Maybe because you cannot use it as a prophylactic, so it doesn't threaten EUA for vaccines?
Ah, for some reason I read the original message as some new dwarf planet was outside our solar system and had a trajectory towards it. Thanks for the clarification.
The "Scottish verdict": https://en.wikipedia.org/wiki/Not_proven
Aw, I thought this was going to be an extrasolar object, but it's an oort object orbiting the sun.

It's also pretty small, about 1/20th the size of the moon. Huge for a comet, but smaller than Ceres.
Is this something we could plan and manage to launch an orbiter/lander to in time? Has anyone thought about the possibility of slapping something like a telescope on that and letting it beam back data and images from veryyyyy far out eventually?
Is it bad for the economy? The labour and supply chain for repair work must add up to an awful lot of people. It’s also going to be paying locals the bulk of the money, where buying a new car is often going to be sending the money off shore.
I’ve been doing something similar. Collecting native seeds from plants that grow well here after they bloom, and distributing them to barren spots that need more growth and color. I just started but hopefully next year there will be more Echium and Lupine around here.
Like the article says: "“It’s too soon to make any firm conclusions about a lot of this stuff, but it sure looks like the mitochondria are disrupted in many kids with autism,” Frye says. “And environmental exposures, especially early on, may be programming the mitochondria to have different types of respiratory physiology.”"

You might find this of interest too from eleven years ago:
https://drhyman.com/blog/2010/12/09/breakthrough-discovery-o...
"Let’s look more closely at what this new study in The Journal of the American Medical Association tells us about mitochondrial dysfunction and how this may lead us to new methods of treatment—methods similar to the ones I used to help reverse Jackson’s autism. ...
This study forces the question: How do children acquire energy deficits that affect their whole system, not just the brain?
The causes of mitochondrial dysfunction are well known, specifically as it relates to metabolism and the brain, and I have documented them in my books UtraMetabolism and The UltraMind Solution. They include environmental toxins(iv)—mercury, lead and persistent organic pollutants(v)—latent infections, gluten and allergens (which trigger inflammation) sugar and processed foods,(vi) a nutrient-depleted diet,(vii) and nutritional deficiencies.(viii) These are all potentially treatable and reversible causes of mitochondrial dysfunction that have been clearly documented.
I found all these problems in Jackson, and over a period of 2 years we slowly unraveled and treated the underlying causes of his energy loss which included gut inflammation, mercury, and nutrient deficiencies. Over time, the tests for his mitochondrial function and oxidative stress (as well as levels of inflammation and nutrient status) all normalized. When they became normal, so did Jackson. He went from full-blown regressive autism to a normal, bright beautiful 6-year-old boy.
This is just one story, but if autism can be reversed in one child, if there is any possibility of effective treatments or a potential cure, it forces us to ask critical questions: How did this happen? Can it happen in other children? What were the biological patterns found and how were they treated?"

And if it applies to young brains, why would it not apply to older brains?
A lot of talk about pages, but no mention about how big these pages are. From a quick look on Google, most SSDs have 4kB pages, with some reaching 8kB or even 16kB.
SDE3 here with 5+ years on the retail side. Listen up new SDE1. Here is the score when you get hired at Amazon. You have 2 to 3 years to get promoted to SDE2 or you are gone. SDE2's you are in the same boat but with less risk of a PIP. You'll need to be making a case for SDE3 in 3 to 5 years or you are going to see you comp decrease over time. Once your at SDE3 you now are really Amazon employee instead of a trainee in the eyes of management. You can more easily push back on stupid management decisions at the L7+ level, except hiring, and use your years of history at Amazon as leverage, most managers are new anyway. Most SDE3s however have figured out that the path to Principal is easier by boomeranging. There are too few L7 level projects to go around. If you want to survive this climb then here are some tips.

1. Really own your product. Know it inside and out. Too many devs rely on tribal knowledge and out dated docs to tell them what they own. The code is the truth, read it, poke at it, review previous CR's and SIMs to piece together its history. You will become the master of the truth.

2. Drive your career. Understand what the moving to criteria for your level are and keep notes for how you are achieving them. Focus on taking on work that gives you more evidence that you are on a promo path. Write the documents that make the argument and iterate on them often. You need to actively manage this or it will manage you.

3. Pushback. Many managers at Amazon are just spreadsheet jockeys that are making things up as they go along. If something is stupid or determental to the product or team say so and have evidence for why. Make the argument and build consensus on the team for that argument. You won't win them all but you will erase from your manager's mind that your are a passive code monkey. The more you do this and can demonstrate results the more you'll have the ability to drive your work.

If you want to be spoonfed a career don't work for Amazon.
A lot of this sounds very familiar. I was working on the in-house tools doing the same thing for a very big VFX house from 2012-2018.
Early on in that job, we only really had one pair of tools for production management - one for the project planning (a big Gantt chart) and the other for timesheeting. There was nothing really in place for the artists to use to know what was going on and as such their willingness to enter timesheets was pretty low.
In order to drive awareness, reduce work for coordinators and generally try to help everyone, I was made lead to bootstrap a new app in 2014 called... ShotGrid. It did help to a degree, it was still mainly only used by coordinators, but helped them do their work slightly more efficiently. We went down that rabbit hole for a while, but still, the artists lacked good tools for connecting with their PMs.
Fast forward to 2016/2017 and my team was sectioned off to completely redesign and rebuild the entire project management tool suite, with the help of some external contractors. Years went by as we did the research, design, technical investigations and review. It was a genuine real struggle to get anyone in the company to engage with us and talk about what they wanted in the product; they'd much rather just struggle on with the existing tools (including endless Excel sheets) and turn their focus to actually doing VFX instead.
I left the company in 2018 amid a lot of frustration about nothing being progressed. I heard about 9 months later that the entire project had collapsed and I think they were then heading towards implementing ShotGun instead.
Which now, ironically, is apparently to be renamed ShotGrid. I'm taking that as a huge coincidence, but it's nice to know that some of the success I had in that industry lives on in name alone.
It is from our solar system. It has just a very eccentric orbit, but it was always orbiting the Sun.

But for interstellar objects, the answer is always "no". Unless it passes very close to some object that there's an orbital slingshot (or a collision, the odds of both are basically zero), interstellar objects always move away.
You should probably read the whole post before replying in clichés.
I'd say what lies at top of the food chain of cause and effect is simply coming from "availability bias" i.e. we give more weight to what we know to be true. Yes some things have more downstream effects than others and that's where you get your bang for the buck.

Whether mitochondria is just one mechanism or more of an over-arching one is what research is all about. For example, HRV feels like on obscure metric out of 100s of metrics. But it has been shown to now have hundreds of mental and physical benefits including longevity, that we don't necessarily understand why but it still has risen to the top. Same for intermittent fasting and so on. These are indeed "weird tricks" in a pretty literal sense but they do the job in predictable and often dramatic ways.
Haxe is one of the very few languages in which a perfect cross-platform widget toolkit could be made. A toolkit that would produce platform-native binaries (no pesky FFI like JNI) using platform specific libraries: targeting Java (maybe even JVM?) for Android, targeting C# for Windows/the-current-Windows-toolkit, targeting Hashlink for Gnome/Gtk, targeting C++ for KDE/Qt, targeting C++ with Objective-C++ for MacOS/Cocoa and iOS/Cocoa Touch. Probably even a web target is viable.

Other language, that it is possible to do with is Scheme, but it is quite a different beast all together.

That's my little dream. I intend to do gobject-introspection bindings one day for it as my first step.
There’s plenty of empirical studies done on animals where we observe they respond to painful stimuli similarly to humans and avoid similar situations thereafter. We can’t ask them so this is the best we have.
It all comes down to how the company is run. We sell our product vs hosting some SaaS, so outages aren't a big deal. We also are not a young company who "moves fast and breaks things", so showstopping bugs are pretty rare.
That's not an argument for not replacing your car, it's an argument for not buying a big car when you do. At least outside the USA it's not hard to buy a new small car.
This is a well-recognised phenomenon.

“Forget GameStop” is a running joke by this point: https://www.reddit.com/r/GME/comments/mhc9vf/dont_forget_to_... — and that post was from nearly 3 months ago. These headlines haven’t slowed down since!

Some people speculate hedge funds are allowing AMC to squeeze, as a way to raise money to cover their GME shorts — not outside of the realms of possibility, given Citadel hold long positions on AMC. The timing of AMC price spikes has also correlated with FTD cycles, but that’s a whole other can of worms.

AMC seems to be covered by the media far more often than GME. On days when GME’s price has rocketed up, there appeared to be media blackouts, and it goes largely unreported. The same thing doesn’t seem to be happening with AMC (at least, not to anywhere near the same extent).

Other common observations include trading apps like Robinhood only sending users push notifications when GME’s price drops significantly — but never when it’s rising. This has not been observed with any other stocks, as far as I’ve seen.
The DRAM you're referring to is for the most part not a write cache for user data. Most of that DRAM is a read cache for the FTL's logical to physical address mapping table. When the FTL is working with the typical granularity of 4kB, you get a requirement of approximately 1GB of DRAM per 1TB of NAND.

Drives that include less than this amount of DRAM show reduced performance, usually in the form of lower random read performance because the physical address of the requested data cannot be quickly found by consulting a table in DRAM and must be located by first performing at least one slow NAND read.
I don’t have any experience with huroku but what most small businesses need is a (perhaps simulated) reliable box on a fast network. As glorious as the paxos based present is, it’s overkill to the point of distraction for most businesses. The whole attraction of the cloud for them is not needing to hire sysadmins. Replacing that requirement with needing a devops team is even worse.
Or much faster (at small sizes): https://github.com/JuliaLinearAlgebra/Octavian.jl
Standard deviation of what group?
Current Amazon engineer.

As others have said, management at Amazon will only direct focus on the development of new features or new services, at the complete detriment of improving existing services, or even the overall architectural design of a particular space of the business. The definition of completing a service or feature is only that a customer is using it without complaint. Management has no interest in technical reasoning, which causes the design decisions that rest at their level to be unreasonable. This leads to a few problems:

1. Services are only ever about 50% complete. Unit tests typically exist to some degree, but integration tests, documentation, complete monitoring and operational automation are rarely done. Services typically have numerous obvious bugs, grossly bad optimization, hideous over engineering, and sometimes design issues. Because the customer cannot detect these things when the first use the service (maybe it will reflect the second time as a bug, or as slow performance later down the line, or long times to develop new features), there is no interest in fixing them.

2. The graph of service dependencies is entirely unmanaged. Any service can depend on any other service, for any reason. This results in a massive, undesigned spaghetti of a system. Something like s3 or whatever will usually be supported in some way by a spaghetti built for s3, and if s3 fails, it is usually not immediately obvious which service in the spaghetti is responsible. It makes adding something new to the overall system take a very long time.

3. Even if a customer is encountering an acute problem, and management is asking for it to be fixed, if the problem is rooted at a system level outside the boundaries of a single service, thus at the level of management, management is unable to engage with any reasoning as to how it should be solved. Only management holds the keys to assigning work (senior or principal devs hold basically zero sway) and thus management must have the technical reasoning ability to make these decisions.

4. Management will sometimes intrude in service level problems and make unreasonable decisions. Examples:

4.1 I was told python is not performant (despite my history at the company having me deploy python code to every single physical host in the fleet) and asked to research and explain why it isn't scalable and we should switch off it. I declined to work on the issue

4.2 Management had an issue raised to them where a single user had sev2ed us because they couldn't paste into a field on our service. Investigation quickly revealed the user was trying to paste text with a space into a numerical field, and the browser was preventing it. The issue already had two solutions suggested: add highlighting to invalid inputs, and strip spaces from inputs. Despite this management decided a formal review was required, where somehow we would have to dig deeper than the existing explanation and explain how this happened and what should be done.
According to TA it is orbiting the sun. The closest point out will be at beyond Saturn's orbit, the farthest will be 30-50k AU. Of course, there are some error bars on these numbers that I can't interpret, and given that it orbits that far out, its orbit might actually be influenced by neighboring stars as well.
I don't think OP was angry. It seemed like a fair question.

I'll bite.

When I was 16, I REALLY wanted to own a motorcycle. I thought they were the coolest.

Luckily, I was pretty poor - so I wouldn't have money for any such thing until I moved from my small town to get a job in Boston. There, I made friends with someone whose father owned a business that put people back together after motorcycle accidents. In just a couple of minutes, he convinced me of how unsafe they actually are. Despite the fact that I think motorcycles are cool as shit - it's hard to argue they are "less safe" than cigarettes for 18 year-olds (or for anyone).

Also, now that I'm older, I definitely wouldn't mind if they were banned on residential streets. At least the ones that are noisy as hell.

So - it's a mix of:

1) It wouldn't be out of line for the Government.

2) It honestly seems in-line for the Government (even if I don't really agree it's what the Government should be doing).

3) It wouldn't affect me personally.

4) Personally, it would actually be a plus since I'm older now and I can't stand the noise.

So as I said - I'm not going to vote to ban motorcycles - and I can't imagine it ever happening - but if it did - you won't see me out in the streets protesting.
> The only thing I'd add is that as you head towards double digit ages

I got too far into this before realising you were referring to cars, not people. It holds up well.

It did have me wondering how early you learned to drive.
What are you building for insurance? I used to be an insurance regulator, still find the space pretty interesting
> But if we extend the notion of learning styles to "some kids lack self-control" or "some kids have trouble keeping attention"

That’s situating the problem in the wrong place. Everyone lacks self control, or has trouble keeping attention depending on the circumstances.

I agree with you that our schools are crap. I also agree that not all kids can be taught everything to the same level.

However that is orthogonal to the notion that kids can be taught to their potential if you allow them to be taught in an appropriate manner.

That ‘teaching styles’ link is accurate, but it deals with a straw man that results from not being willing to question the constraints of school.
> Who in their right mind does math on a computer, math is implemented on a computer, but it's done by hand.

Maybe you think this becuase your used to writing math on computers that make writing that math ugly and obtuse?

Besides, having the math you've written by hand closely match the syntax you use on the computer can greatly reduce the cognitive burden of switching between code and paper.
How can a hypothesis be a lie at all? A hypothesis is either worth investigating or not worth investigating. By the very nature of hypothesis, we don't know if they will eventually turn out to be proven correct or incorrect.
> And lets say each vaccine harms you just a tiny bit, which they clearly do

I don’t think this is supported by evidence at all.
https://archive.is/1IE45
Once the pandemic phase is over, it'll be yet another endemic disease, meaning that as time goes anyone's chance of getting it tends towards 100%.
Why do I need to know lisp in 2021? Any practical real use besides being used as example in books about computation?
You're right that the FTL has some durability concerns which, in addition to performance, is why it's typically cached in DRAM. Older DRAM-less SSDs were unreliable in the long-term but that's been improving with the adoption of HMB, which lets the SSD controller carve out some system RAM to store FTL data.