brandishwar

With dual CPU, you have the NUMA node barrier. And the PCI slots on multi-CPU boards are split between CPUs as well. So you might have quad-SLI, and it looks like quad-SLI to the NVIDIA driver, but it's more like dual-SLI due to how the PCI-E slots are actually wired up. That NUMA node barrier also means that any data going across to the other graphics cards needs to go across to the other CPU to the GPUs in question across the second CPU's PCI-E lanes. That's.... painfully slow. I'm actually surprised Windows was actually allowing it to happen, to be honest. Having a single CPU with triple or quad-SLI would've been better to avoid the NUMA node limitation, but then you likely still would've been CPU limited simply because the CPU likely couldn't keep up with trying to coordinate 4 GPUs in SLI. ETA: Okay scrap the above since that doesn't apply since those old CPUs didn't have the PCI-Express lanes handled by the CPU directly. It's handled by the chipset, which is obviously slower. The Intel 5520 chipset supports only PCI-E 2.0, and the GTX 900 series is where 2.0 vs 3.0 really started to matter, along with lane counts. And the chipset provided a max of 32 lanes and the mainboard uses an NF200 bridge chip (similar to a PLX) to spread that out.

THANK YOU, THANK YOU, THANK YOU for not just the content warning about the flickering colors and text with the Wireshark demo, but also the audio chime for when it was safe to look at the video again. Definitely keep doing that in the future! It's something I wish more content creators took into account.

Oh dear God, this had to have been one of the only LTT videos where I was yelling at my screen... Why didn't you go to a hardware store and find plumbing fittings that would've properly fit the inlets and outlets on that radiator? Using a tire inner-tube and zip ties?!? Really?!? I mean you had to order in the radiator, so why didn't you take additional time to find all the proper parts that would've allowed you to do this somewhat properly? And then you had the output on the pump going to the GPU block rather than just straight up to the radiator? That would've eliminated most of the flow resistance since gravity would've given you flow pressure on its own given the mass of the fluid you would've had in that. Or, better yet, NOT having the radiator ABOVE the entire system! This had so much potential that was just.... wasted.

Are hard drives still worth it? I don't even need to watch the video to say this: YES! Price per TB for HDDs is still unbeatable and will remain such for the foreseeable future. And combining them into a RAID setup (whether in your case or via an external enclosure) will still net pretty decent performance as well as capacity, making them a great choice for a large game or media library or on-site backups.

And I'm guessing the takedown notices and "cease and desist" letters are already on the way to everyone involved...

That's been my thought watching this "adventure". I use optical fiber for 10GbE in my home. (With exception of 1 short DAC that goes from a MikroTik CSS610 to my CRS317). I used to have them hanging on the walls and just yesterday ran two through my attic to get between a hallway closet (networking equipment) and the rack (NAS, virtualization server). And I certainly wasn't "gentle" in doing that. You don't need to baby the fiber cables the way they were trying to hook up the ingest stations.

This is one of those topics for which history is a necessary part of the discussion. Since in doing this experiment, you basically ignored the advances in PCB design that allow for better ESD protection, along with published standards for minimizing ESD risk. This is about on par with the whole "cable management doesn't matter" video you made in which you used a modern chassis with several 120mm fans for airflow, completely ignoring the history of the concept and recommendations. There are several things that protect against ESD, all of which are likely integrated into those DDR2 RAM sticks, and all of which you basically had to overwhelm to kill them. This includes a ground plane along with other components as part of an overall grounding strategy that aims to minimize the risk of ESD to sensitive components. There are published guidelines and standards for ESD protection and grounding. A simple Google search would've provided that information, which would've informed you on WHY you had to go to some extreme lengths to kill the RAM sticks, and why your initial attempts weren't working as well as you thought. This doesn't mean you should be careless in handling PC components, but it does mean you don't need to be paranoid. But there was a time where paranoia of ESD was necessary, but it's been quite a long while since that was the case.

Computers aren't the only thing that are water cooled. I recall seeing a project years ago where these small radiators were used in RC vehicles.

"Software as a service" I know gets a bad rap in the industries where it's become prominent, but it's also allowed for a lot of leeway when it comes to software pricing. For example, Microsoft Office had a hefty price tag to it before Office 365 came along at $100 per year for 5 machines (with different tiers as well). And that Office 365 license provides everything that was part of Office Professional. And Microsoft has also largely moved toward the "Software as a service" model for their other professional suites like Visual Studio - though with VS they also have the community editions available which have enough functionality for most developers who aren't working on enterprise-level software. And from Microsoft's perspective, it's likely much better for their bottom line to have customers paying for a monthly or annual subscription than paying one price up front every however many years, especially if it brings more customers onboard. And that subscription also includes technical support, whereas that support would expire after a short time with the "buy once" model. So there are trade-offs either way. Adobe's software suite is similar in that regard. I pay $10 for Lr CC with 1TB online storage. I've considered including Ps in that as well, but I don't mind exporting to 16-bit TIFF to use GIMP for the few places where I do need it. It's what I used to do with Nikon's software before I bit the bullet and went with Lr, as it was much easier to learn Lr than learn how to do the same in GIMP.

You can also find used options through mpb.com and KEH. I've ordered through the former a couple times and also sold to them, and I've heard a lot of good about the latter, and both have good reputations.

Sounds like they also don't make that easy to do. So hopefully that's something Folding@Home will be changing so they can allow volunteers to set up servers. But then the workers are intended to be able to come and go. Servers have to be dedicated.

Right, and now that I know why you're wanting to parse the example line in question, knowing where it came from, I'm pointing you to an easier method of reading and writing the .INI file that abstracts away reading the file, reading the line, and parsing the line. Sometimes knowing the full scope of the problem you're trying to solve allows us to point you to solutions that are a lot simpler than whatever you're considering. So if you're now going to be trying to implement a .ini file parser, reconsider doing that.

So you're trying to parse an INI file? If you're doing this on Windows, there's already an API that'll do all the parsing for you without you having to handle the actual file contents: https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-getprivateprofilestring

As long as nothing conductive touches it and creates a short, you don't really need to worry about it.

Short answer: no. Long answer: Whether you can use registered DIMMs is dependent upon the mainboard, not the CPU. Try to use RDIMMs on a mainboard that doesn't support it and the system won't POST. And since the memory controller is embedded in the CPU, it's likely that attempting to use ECC RAM with a CPU that doesn't support it will give you a system that won't POST.