News for hackers. Stuff that matters.
Re:Prefix sum: 20 GB/s (2.6x baseline) by yogishbaliga on Tuesday October 14, 2025 @02:54PM (#45583466)
Way back in time, I used delta encoding for storing posting list (inverted index for search index). I experimented with using GPUs for decoding the posting list. It turned out that, as another reply mentioned copying posting list from CPU memory to GPU memory was taking way too long. If posting list is static, it can be copied to GPU memory once. This will make the decoding faster. But still there is a bottle neck of copying the result back into CPU memory.

Nvidia's unified memory architecture may make it better as same memory can be shared between CPU and GPU.

Re:Prefix sum: 20 GB/s (2.6x baseline) by Certhas on Tuesday October 14, 2025 @02:58PM (#45583498)
AMD has had unified memory for ages in HPC and for a while now in the Strix Halo systems. I haven't had the chance to play with one yet, but I have high hopes for some of our complex simulation workloads.
Re:Prefix sum: 20 GB/s (2.6x baseline) by ashtonsix on Tuesday October 14, 2025 @03:04PM (#45583550)
Oh neat. I have some related unpublished SOTA results I want to release soon: PEF/BIC-like compression ratios, with faster boolean algebra than Roaring Bitsets.
Re:Prefix sum: 20 GB/s (2.6x baseline) by hughw on Tuesday October 14, 2025 @04:37PM (#45584525)
The shared memory architecture doesn't eliminate copying the data across to the device. Edit: or back.
Re:Prefix sum: 20 GB/s (2.6x baseline) by yogishbaliga on Tuesday October 14, 2025 @06:23PM (#45585756)
If it is unified memory, CPU can access the result of GPU processing without copying it to CPU memory (theoretically)
Re:Prefix sum: 20 GB/s (2.6x baseline) by hughw on Tuesday October 14, 2025 @06:35PM (#45585858)
If the CPU touches an address mapped to the GPU doesn't it fault a page into the CPU address space? I mean the program doesn't do anything special, but a page gets faulted in I believe.