Menu

#Fp16

10 posts

Feed·
10 of 10 posts
Silent NaN: the check that belongs in every diffusion pipeline
📰
0Read More

Silent NaN: the check that belongs in every diffusion pipeline

DEV Community: python·mujin·7 days ago
#Mwm4z8go
#devtopython#devto#dev#file#fp16

I generate 512x768 images on a 4GB GTX 1650. About 150 seconds per image in fp32 with model offload....

15s
Modders unlock hidden AI power on Nvidia RTX 20, 30, and 40 series GPUs, nearly doubling some benchmarks
🖼️
0Read More

Modders unlock hidden AI power on Nvidia RTX 20, 30, and 40 series GPUs, nearly doubling some benchmarks

#techspotnews#technology#techspot#cards#card

The limit lives in the tensor cores. When they multiply FP16 or BF16 numbers and add up the results in higher-precision FP32, GeForce cards issue those instructions...

15s
Accelerating BEV Pooling on NVIDIA GPUs for Physical AI Applications
🖼️
0Read More

Accelerating BEV Pooling on NVIDIA GPUs for Physical AI Applications

NVIDIA Technical Blog·John Yang·17 days ago
#AdDuo8jV
#developer#scatter#path#fp16#pooling

An increasingly common design pattern for autonomous vehicles (AVs), robotics, and spatial AI systems is bird’s-eye-view (BEV) perception.

15s
GitHub - huawei-csl/KVarN: KVarN is a native vLLM KV-cache quantization backend for your agents: 3-5x more context, throughput above FP16, and FP16-level accuracy. Calibration-free, one flag.
🖼️
143Read More

GitHub - huawei-csl/KVarN: KVarN is a native vLLM KV-cache quantization backend for your agents: 3-5x more context, throughput above FP16, and FP16-level accuracy. Calibration-free, one flag.

Hacker News·5 months ago
#1P7kvTiP
#github#kvarn#cache#vllm#capacity

KVarN is a native vLLM KV-cache quantization backend for your agents: 3-5x more context, throughput above FP16, and FP16-level accuracy. Calibration-free, one flag. - huawei-csl/KVarN

15s
0Read More

Technical question about Mamba Selective Scan kernel and FP16/FP32 precision

Reddit r/learnmachinelearning·u/Dry-Trouble4373·7 months ago
#kGw7XvYx
#kernel#fp16#mamba#fp32#precision

I'm trying to evaluate the model's accuracy when all internal operations are strictly limited to **FP16**. However, I noticed that the `selective_scan` CUDA kernel seems to use **FP32 accumulators** by default.…

15s