An optimization with a universal >=0 speedup across your entire suite of tests is a really hard thing to come by. Something is always going to have a negative speedup.

My experience is with non-Nvidia GPU systems, but this feels like a familiar situation. They probably found something that has great outcomes for one set of kernels, terrible outcomes for another, and no known reliable heuristic or modeling they could use to automatically choose.

I think a very high application fee is actually part of a good solution, but is useless by itself.

A flawed proposal:

* Dispense with the 'need to search for a qualified American' which just complicates the process without achieving the stated goal, and includes a ton of legal and bureaucratic expense and time.

* A large application fee paid from the company to the federal government.

* The worker's relocation expenses must also be covered by the company.

* The worker gets a 10 year work authorization on the day of their arrival.

* The worker gets to leave their sponsoring employer on the day of their arrival, if they choose to. The employment contract may not include any clawbacks of anything.

The latter bullet is the key one. That's the one that uses market forces to truly enforces this person is being paid above market wages, and is being treated well, at their sponsoring employer. (which in turn means they don't undercut existing labor in the market).

It also means that employers don't really look abroad unless there really is a shortage of existing labor. But when there is a true shortage and you're willing to spend, the door is open to act quickly.

The obvious defect is that it creates an incentive for the employee to pay the federal fee themselves (hidden) plus more for the privilege of getting sponsored, and the company basically being a front for this process. Effectively buying a work authorization for themselves. I'm not sure how to overcome that. Then again, the current system could also suffer that defect (I don't know how common it is).

That isn't predictive at all of NMC or LFP chemistries though (and I'm not going through multiple charge cycles per drive), but a fun anecdote. It was an entertaining project opening up the battery pack and identifying/replacing the bad modules.

In the end, other parts of the car were dying too, and the final straw was California's refusal to allow aftermarket catalytic converter replacements, and the Toyota's price (with no competition) was more than the vehicle was worth.

So far my two EVs, both NMC chemistry (Kia and Rivian) are at 80,000 and 30,000 miles respectively, with no noticeable degradation.

Comments URL: https://news.ycombinator.com/item?id=44063635

Points: 4

# Comments: 0

If you go to Settings -> Privacy, the top two options in iOS 18 are:

* Auto-deny Advertising ID access

* Which apps have location access ("X always, Y while using the app" is summarized right at the top)

My own policy has two drivers with a long flawless history, and several vehicles, including a heavy duty pickup truck and a compact crossover.

The truck policy prices for bodily injury is 8% higher than the crossover, while property damage coverage costs 20% less for the truck.

There appears to be a material difference in conclusion between my insurance underwriters and the producers of these studies on the danger of these vehicles.

With a search warrant, they can. You can be kept out of your home until they complete the search and seizing of the items named in the warrant. Depending on what is being searched for (excavating your basement looking for bodies?) that could take quite some time.

So the Tesla situation getting press isn't because the precedent is new, it's because most Americans (many in this thread included) don't understand what the law has already been since long before Teslas ever existed, and are surprised at what they find.

But if that doesn't work, then preserving evidence is considered to be very important. For example, it would be a problem if the car owner deleted the video.

But in general, this isn't really much new. If you have home cameras, and police can obtain a search warrant, then you can be compelled to provide the video, or they can seize any device (such as entire computer, your server closet, etc) that could reasonably contain the video.

https://www.energy.gov/eere/vehicles/articles/fotw-1329-febr...

In these difficult scenarios, the alternative photo I'd get using such a small camera without this kind processing would be entirely unusable. I couldn't rescue those photos with hours of manual edits. That may be "in control", but it isn't useful.

These are two excellent posts that go deep on this:

The Shader Permutation Problem - Part 1: How Did We Get Here?

The Shader Permutation Problem - Part 2: How Do We Fix It?

In particular, the second post has the line:

  We probably should not expect any magic workarounds for static register allocation: if a callable shader requires many registers, we can likely expect for the occupancy of the entire batch to suffer. It’s possible that GPUs could diverge from this model in the future, but that could come with all kinds of potential pitfalls (it’s not like they’re going to start spilling to a stack when executing thousands of pixel shader waves).

https://therealmjp.github.io/posts/shader-permutations-part1...

https://therealmjp.github.io/posts/shader-permutations-part2...

They are low utilization, but apparently still worth it because process node changes have made more ALUs take relatively little area. So doubling the ALU count, even with low utilization is still apparently an overall benefit (ie, there wasn't something better to spend that die space on).

A "Core" (Apple's term) / "Compute Unit" (AMD) / "Streaming Multiprocessor" (Nvidia) / "Core" (CPU world). This is the basic unit that gets replicated to build smaller/larger GPUs/CPUs

* Each "Core/CU/SM" supports 32-64 waves/simdgroups/warps (amd/apple/nvidia termology), or typically 2 threads (cpu terminology for hyperthreading). ie, this is the unit that has a program counter, and is used to find other work to do when one thread is unavailable. (this blurred on later Nvidia parts with Independent Thread Scheduling.)

* The instruction set typically has a 'vector width'. 4 for SSE/NEON, 8 for AVX, or typically 32 or 64 for GPUs (but can range from 4 to 128)

* Each Core/CU/SM can execute N vector instructions per cycle (2-4 is common in both CPUs and GPUs). For example, both Apple and Nvidia GPUs have 32-wide vectors and can execute 4 vectors of FP32 FMA/cycle. So 128 FPUs total, or 256 FMAs/cycle Each of these FPUs what Nvidia calls a "Core", which is why their core counts are so high.

In short, the terminology exchange rate is 1 "Apple GPU Core" == 128 "Nvidia GPU Cores", on equivalent GPUs.

Even if DOTS was perfect, the GPU would still be entirely geometry throughput bottlenecked.

Yes, UE5 has a large competitive advantage today for high-geometry content. But that wasn’t something Unity claimed could be automatically solved (so Unity is in the same position as every other engine in existence apart from UE5).

The developer should have been aware from the beginning of the need for geometry LOD: it is a city building game! The entire point is to position the camera far away from a massive number of objects!