News for hackers. Stuff that matters.
Re:Show HN: ChartGPU – WebGPU-powered charting library (1M p... by akomtu on Wednesday January 21, 2026 @03:11PM (#46710899)
At 1M points it hardly makes a difference. Besides, 1 point -> 1 pixel mapping is good enough for a demo, but in practice it will produce nasty aliasing artifacts because real datasets aren't aligned with pixel coordinates. So you have to draw each point as a 2x2 square at least with precise shading, and we are back to the rasterizer pipeline. Edit: what actually needs to be computed is the integral of the points dataset over each square pixel, and that depends on the shape of each point, even if it's smaller than a pixel.
Re:Show HN: ChartGPU – WebGPU-powered charting library (1M p... by dheera on Wednesday January 21, 2026 @05:31PM (#46712566)
Aren't we at petaflops now with GPUs? 1M or even 1G points should be no issue if it renders to a framebuffer and doesn't go through mountains af JS framework rubbish followed by mountains of GTK/Qt/.NET rubbish.
Re:Show HN: ChartGPU – WebGPU-powered charting library (1M p... by rustystump on Wednesday January 21, 2026 @11:29PM (#46715332)
Not true. Fill rate and memory speed is still a huge bottleneck. The issue is not “rubbish” but memory speed. It is almost always memory speed, cache, ram, disk etc.

There is this misconception that if one uses js or c# to tell a gpu what to do it is somehow slower than rust. It only is if you crunching data but moving memory to the gpu and telling gpu to crunch is virtually identical.

Re:Show HN: ChartGPU – WebGPU-powered charting library (1M p... by dheera on Thursday January 22, 2026 @12:47AM (#46715738)
PCIe 6.0 x16 delivers ~128 GB/s so the billion points can be loaded in milliseconds onto the GPU. The GPU's memory is much faster.
Re:Show HN: ChartGPU – WebGPU-powered charting library (1M p... by rustystump on Thursday January 22, 2026 @03:23AM (#46716579)
Most consumers dont have that and at 60 fps you are already maxing it out and more assuming os is doing nothing else. Bandwidth even on gpus is still the bottleneck.

Even then, when u write to a framebuffer directly in the gpu if the locations of the points are not contiguous you are thrashing. Rendering points very fast is still very much about reducing the data set down to bypass all the layers of memory walls.

Re:Show HN: ChartGPU – WebGPU-powered charting library (1M p... by dapperdrake on Thursday January 22, 2026 @08:49AM (#46719211)
No difference for human visuals or no difference for discrete data or no difference for "continuous" f32 data?