• 0 Posts
  • 26 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle
  • My main point though is that it isn’t the electronics or the fan’s max speed that are the critical parts, it’s whether the fan is able to dissipate the heat being generated with the total sum of how everything is set up. If it can’t, then temperature creeps up until that max speed is hit (thus it can’t dissipate anymore and throttles, hits equilibrium at a higher temperature (because bigger temperature differential means more heat transfer even at the same fan speed, so it’s possible it won’t just run away when the max speed is hit), or melts/overheats to failure) or until the fan speeds up and is able to find an equilibrium or reduce the temperature.

    Thus whatever tricks they use need to result in fans that are still good enough to replace whatever fan they are replacing or they will cause performance issues.

    Though if someone is just adding case fans, then as long as it doesn’t disrupt the airflow, it will help even if it isn’t very good, and you can use multiple quiet fans to replace a single loud one and see an overall improvement even if the individual fans aren’t nearly as good as the single one they replace. So based on that, I’ll back down from my previous “their reputation speaks for itself” because the reality is that they can be overpriced underperforming garbage but still get a good reputation because they aren’t just being evaluated via a/b testing and I was naive to oversimplify it like that.


  • You were downvoted because you’re wrong, or at best technically accurate but inaccurate about the results.

    Your fan speed is set by your fan controller.

    And while it’s true that different fans can be set up to spin at different speeds with the same input voltage or PWM signal, if the fan is less effective at cooling at that rate, the controller will end up higher on the fan curve and speed it up to compensate.

    The only things that determine your fan’s ultimate speed are a) how high the controller allows it to go, b) how much heat the hardware is generating, and c) how efficiently the combination of coolers and fans dissipate that heat into the air (which also depends on the room’s conditions).

    Now we’re just talking about fans, so we can ignore item b entirely as well as the cooler and room conditions. And it then comes down to, can the fan keep up with the heat being generated at the current point in the fan’s curve? If not, heat increases and the controller speeds up the fan. Then, when it hits whatever the cap is, if it still can’t keep up, the hardware either overheats or throttles.

    If it can keep up, then it stays where it is on the curve. If it can dissipate more heat than is being produced, it goes down on the curve and the fan slows down as the temperature lowers.

    All this to say, if you have fan A that needs to be at 2000 rpm to keep up with the heat being generated by the hardware at say 65°C and someone says they have a better fan, B, that is just set to spin slower at the same signal from the controller, all that will happen is it will fail to keep up with the heat generated at 65, then the heat will rise until it’s spinning at 2000 rpm anyways or the curve hits the cap and the system throttles to reduce the heat generated.

    So we couldn’t really eliminate that item b above and it could actually be relevant, though if that were the case, I’d assume people would just curse noctura because their fans suck and their systems run hotter or slower. But they have a good reputation where the main complaint I see is about their price, not their performance.

    Personally, I use be quiet! fans rather than noctura, but it’s a similar principle. They make quieter fans by tweaking or redesigning blades shape and angle, bearings, and the motor. Blades make them more effective at slower speeds, and all three can make them quieter at the same speeds.


  • Yeah, just to add some context, you can detect potential buffer overruns in code by looking for patterns but just because you find potential buffer overruns doesn’t mean they are exploitable. The user needs to be able to inject not just code or parameters but also a return address that causes the injected code to run or triggers another function call with the injected parameters. With randomized code and stack addresses, this can be difficult or practically impossible, even if it’s easy to customize what bytes go into the overrun part of the buffer.

    It’s like finding small parts of dangerous patterns but those small parts aren’t necessarily dangerous on their own and need more of the pattern to be an issue, but if you fix the small parts you find, you’re less likely run into those bigger patterns, so it’s worthwhile to fix the small patterns when they come up, but without fitting into a larger pattern, it wasn’t an actual security hole, just a potential one.




  • I remember years ago there was a firmware source leak (or maybe the binary was analyzed or something) for gigabyte’s led controller firmware/drivers that basically just exposed the firmware programming bus to user land because that’s how they did lighting updates and the kernel mode driver just passed whatever the user mode driver gave it, which could include firmware updates to other hardware IDs.

    It was at this point that I stopped running a lot of those hardware control utilities (and I suspect that might also be why I barely saw any issues with the Radeon 5700 XT that was a bit infamous for “its” issues that I think might have just been incompatibilities with 3rd party “helper” utilities or shit written by companies that had gotten to the “just ship it” stage of development).





  • In general, trying to split up frame rendering between multiple GPUs runs into issues with latency because either you need to share data between the GPUs (so some reads/writes go to the remote GPU, which takes longer and then there’s cache coherency issues on top of that) or you need to mirror it (so all data transactions between GPU and CPU need to be doubled, bus bandwidth might need to be shared), and there could still be cross-gpu dependencies that require eating those longer latencies.

    100 fps means each frame needs to be rendered in 10ms, so even round trips of 1ms can be costly and risk missing the frame deadline (which results in a stutter). The whole idea of multi-gpu is to get even higher frame rates, so the higher they get pushed, the bigger an impact that latency has.

    Though maybe raytracing workloads would work well with it. Something that depends more on massive parallelization than anything else and where each ray is independent. But load balancing still isn’t trivial as it will depend on the scene or even the camera and lighting position and the software complexity might not be justified by how small the market would be.







  • Yeah, it’s either that or someone who has decided their special interest is hating linux. If it’s the user that I think it is, when I looked at their history earlier, pretty much every post of theirs is over the top anti-linux.

    Though I am glad to see that most of the accounts I suspect of astroturfing are generally downvoted to the negatives here. Though I do wonder if this place will end up being a training ground for propaganda that works on the segments of the population that are highly represented here that don’t seem as susceptible to the shit that would get eaten up on FB or gain some traction on reddit. Actually, windows love probably does well on reddit since it’s made up of people who haven’t gotten tired enough of the enshitification to leave and are probably doing the same with windows.

    That… might even be why they enshitified it so much for no apparent benefit at the cost of many users that contributed positively. Those contributions might not have been seen as so positive if they responded to marketing bullshit negatively.