Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CUDA Toolkit Release Notes

docs.nvidia.com

Post reply on HN
Print view View original

101–110 of 126 posts

Re: CUDA Toolkit Release Notes

#101

Post by pvg »

andybak wrote: post #97
pvg wrote: post #56

Earlier quoted context omitted.

For 1., again, the standard isn't 'someone might not have known a detail in the story', it's 'does the title represent the story'. If that particular detail is worthy of highlighting, it's easy to find (or even write!) a story about that or point it out in a comment. For 2., that's been the unfortunate case for ages but more importantly, see 1.

It's not a "detail" if it's pretty much the only reason to post or read the story in the first place.

Sure, it might be an important detail to you but that's just not how titling HN stories works, as explained at great length in the thing linked in my comment and many other places.

Re: CUDA Toolkit Release Notes

#103

Post by [deleted] »

benologist wrote: post #98
sbuk wrote: post #95

Earlier quoted context omitted.

So, you are aguing that NVidia constantly messing up when Apple have used them in good faith as a supplier, followed by the subsequent denial of problems even existing by NVIdia and their refusal to accept any culpability (see Bumpgate), is "a very one-sided take" and eschew it in the belief that this is all about pushing Metal? That seems like the very narrowly held view to me. Perhaps they are thinking the way you…

Nearly a decade has passed since nVidia messed up one generation of laptops so probably it's time to let it go. Grudges don't really help anyone, and Apple's so far from innocent they shouldn't promote grudges as solutions to problems, especially as alternatives to consumer-friendly hardware support. In much more recent times Apple themselves ruined four generations of laptops and were deceptive and dishonest about i…

[deleted]

Re: CUDA Toolkit Release Notes

#104

Post by minimaxir »

jsgo wrote: post #73
pvg wrote: post #53

Earlier quoted context omitted.

As the whiner who whined about this title - the story isn't worthy of note at all, other than someone fishing a supposedly-important detail out of it and putting it in the title. Apple hasn't as much as sold a machine with an Nvidia GPU for many years. This non-editorializing thing is explained in great illustrative detail here: https://news.ycombinator.com/item?id=21617907

Perhaps they haven’t sold Nvidia hardware, but the allowance of Nvidia’s web drivers so that I could connect my eGPU w/ GTX 1080 to the 13in Macbook Pro was one of the primary reasons I bought the MBP. It is fine if they want to kill off features off upcoming hardware, but killing off the capacity to use something that was used for months is not the best look. If Metal Only was the goal, add a prompt when someone ena…

Even AMD eGPUs have a lot of compromises (e.g. HDCP issues), although those may or may not be Apple's fault.

I bought a lower-spec MBP with the expectation of using eGPUs (in the hope Apple and Nvidia would make up), but it's good to see it confirmed that it won't be worthwhile.

Re: CUDA Toolkit Release Notes

#105

Post by [deleted] »

benologist wrote: post #98
sbuk wrote: post #95

Earlier quoted context omitted.

So, you are aguing that NVidia constantly messing up when Apple have used them in good faith as a supplier, followed by the subsequent denial of problems even existing by NVIdia and their refusal to accept any culpability (see Bumpgate), is "a very one-sided take" and eschew it in the belief that this is all about pushing Metal? That seems like the very narrowly held view to me. Perhaps they are thinking the way you…

Nearly a decade has passed since nVidia messed up one generation of laptops so probably it's time to let it go. Grudges don't really help anyone, and Apple's so far from innocent they shouldn't promote grudges as solutions to problems, especially as alternatives to consumer-friendly hardware support. In much more recent times Apple themselves ruined four generations of laptops and were deceptive and dishonest about i…

[deleted]

Re: CUDA Toolkit Release Notes

#106

Post by keldaris »

sorenjan wrote: post #69
suyash wrote: post #22

We need a CUDA alternative for non NVIDIA gpu's, specially on a Mac.

I recently looked into GPGPU programming, and it seems to be a bit of a mess, which is surprising seeing how long it's been around and how much it is used. I think a large part of it is due to Nvidia using their strong position to hamper anything other than Cuda. OpenCL 2.0 was announced in 2013, Nvidia added OpenCL 2.0 "for evaluation purposes" in 2017. I don't think they have final support yet. OpenCL 2.1 uses the…

As you've correctly identified, CUDA is the only sane default choice in the GPGPU world. OpenCL 1.2 is a viable distant second if you're sure you don't need any of the major CUDA libraries and value the portability aspect (not the same thing as performance portability, of course, but still). Finally, if you don't need strict accuracy guarantees and your application is mostly about graphics, you can get by with compute shaders. Everything else - POCL, HCC, ROCm, the various SYCL implementations, etc. you can safely ignore if you want something usable today, none of them are production ready or anywhere close to it.

Re: CUDA Toolkit Release Notes

#107

Post by dang »

sergiomattei wrote: post #91
andybak wrote: post #43

Earlier quoted context omitted.

Any title that gives us a clue why the story is worthy of note. At the moment it's frustrating as you have to click through to find out if you want to click through. (title at the time of my comment was "CUDA Toolkit Release Notes")

Agreed. Quite frankly the new title doesn't help people understand why it's newsworthy.

By the time we changed the title, the comments were making that quite clear.

Re: CUDA Toolkit Release Notes

#108

Post by dang »

Tenoke wrote: post #45
dang wrote: post #19

Submitted title was "Nvidia drops support for CUDA on macOS". We changed that for a while to "CUDA 10.2 is the last release to support macOS", which is language from the article itself. Since then someone emailed and asked why the title was like that in light of the discussion at https://news.ycombinator.com/item?id=21617016 , so I've reverted to the article's title. Edit: If the article were more a burying the lede…

Why is the threshold for changing urls and titles lowering all the time? It seems like it has went from something rare, only used in very clearcut cases to something you use daily.

That is sample bias. HN moderation of titles and URLs has been the same for many years. It was never rare, and was always happening daily.

Re: CUDA Toolkit Release Notes

#109

Post by semi-extrinsic »

gambiting wrote: post #77
semi-extrinsic wrote: post #65

Earlier quoted context omitted.

I'm not so sure I agree. My old laptop (still in use) is a Dell Precision m4800. It has a quad-core i7, and is so thick and heavy the word "laptop" is kind of a joke. It has massive heatsinks and fairly loud fans. Still it will throttle back after ~90 seconds of "make -j 4" or other heavily parallel jobs. If you have a laptop that will run at 100% load indefinitely, it's only because the manufacturer has chosen a low…

Well, then you need to look a little bit longer around the market. At work we use Eurocom laptops with desktop-grade i7 and i9s rated at 90W of power - and we use them for conferences and trade shows to run our demonstrations, they do absolutely fine under full load. Sure they weigh about 5KG, but that's absolutely fine for the target use. I hope that answers the question of "why would you possibly want to do that".…

Those Eurocom laptops look neat, thanks for the tip.

I'm just a bit surprised if they manage to squeeze out significantly better thermal performance than Dell does out of a similarly bulky laptop.

Have you actually verified the core frequencies over time with a tool like CPU-z when running a workload that pegs all cores at 100%?

The Precision model I have doesn't stutter or feel any slower under load. I've never managed to make it feel slow, even when running heavy physics simulation codes on all cores in the background. But when you actually monitor frequencies, you see it clocks down by around 20%.

Re: CUDA Toolkit Release Notes

#110

Post by mroche »

ktm5j wrote: post #84
amelius wrote: post #83

I'm using CUDA under Ubuntu, and have noticed that the CUDA library uninstalls itself every so often. Has anyone else experienced this?

You probably installed a kernel update and the nvidia kernel module didn't recompile itself. You can avoid having to reinstall the whole driver package by just running "dkms autoinstall" and then "modprobe nvidia" You may first need to unload any loaded nvidia modules (built for an older kernel).. So some combination of "rmmod nvidia_modeset" "rmmod nvidia_uvm" "rmmod nvidia_drm" "rmmod nvidia" and then run dkms I ru…

What distro are you running in your labs? At my university’s cluster running with RHEL 6 (same applies to RHEL 7, hopefully they managed the upgrade over the summer) all that’s needed is installing dkms, then the CUDA repo from NVIDIA, which includes the driver and CUDA packages. Any kernel update will rebuild the kmod on reboot. I’m not 100% certain if that repo is Tesla cards only (which is what we were) but ELRepo also has the generic driver and associated bits (same as negativo, but those are very granular). DKMS is really the only piece that’s necessary to keep the system running (other than keeping an eye on which kernel version the kmods were based on if using the non-NVIDIA repo). DKMS also works just fine with the NVIDIA provides installer, just make sure you have the libglvnd bits installed before you install the driver.
Post reply on HN