cuda-samples VS Remotery

installing, building, and running WSL CUDA examples from https://github.com/nvidia/cuda-samples

After which nvcc should be accessible to new sessions, and you can build C++ cuda stuff like cuda-samples. Python packages like pytorch should also see CUDA and be able to use it.

I haven't found any note that these APIs do not support Windows, and it also seems that the memMapIPCDrv CUDA sample supports Windows.

I installed nvidia-cuda-toolkit and tried to build https://github.com/NVIDIA/cuda-samples but I'm getting stupid errors... it installed nvccat /usr/bin/nvcc and the samples expect /usr/local/cuda/bin/nvcc... symlinking it to that location and it dies with

Can build the cuda-samples, then you have a working nvcc.

I have installed cuda and cudnn, and was testing the installation with the cuda-samples, as the Arch Wiki suggested. But, I am not able to get samples like nbody, smokeparticles, Mandelbrot, etc. to run. Although devicequery works fine, and I get the expected output, so I think there is not a problem with my cuda installation.

Hi, I don't have much experience with Nvidia Jetsons. You can find some examples on GitHub (here https://github.com/NVIDIA/cuda-samples). You can find CUDA implementations of most functions on the internet though, you just have to look for the specific thing you are looking for. Cuda kernels are not platform specific, they should work on GPUs and embedded developer boards without problems as long as you respect the limits imposed by the "compute capability" of your device, you just have to compile your code using the right architecture flag. The biggest limit you have to deal with when developing for Jetson nano is the low amount of memory.

—> git clone https://github.com/NVIDIA/cuda-samples.git —> cd cuda-samples/Samples/1_Utilities/deviceQuery/ —> make —> ./deviceQuery (Result=pass?good) —> cd ~/ —> wget https://repo.anaconda.com/archive/Anaconda3-2021.11-Linux-x86_64.sh

is this the source code that u are talking about ? : https://github.com/NVIDIA/cuda-samples ? I dont see any CMakeLists.txt inside...

Remotery - https://github.com/Celtoys/Remotery

Visual Studio's built-in profiler is an ok sampling profiler. It doesn't give you a nice multi-thread view which is a huge advantage to a span based profiler.

MTuner is quite nice for debugging memory usage. Which is another gaping hole in the Rust ecosystem. https://github.com/milostosic/mtuner

Lots of tools generate data in a format viewable by the Chrome trace viewer. I think Chrome's tracer viewer is not great. Maybe someday someone will create a viewer for the format that's good. I get cranky when large traces don't render at 60fps. Web-based viewers are almost all very very slow and it makes me sad.