Rayforce

Posted by tosh 3 days ago

Counter25Comment7OpenOriginal

Comments

Comment by arikrahman 3 hours ago

Any relation to the smash hit SHMUP of the same name?

Comment by viktorsovietov 3 hours ago

No

Comment by cma256 3 hours ago

> Rayforce is a library you link, not a server you deploy. The C API is small enough to wrap from any language with an FFI.

I'm familiar with large-scale, commercial, client-server use cases for columnar analytics and graph traversal but what is the use case for an embedded server like this?

Comment by hetoku 3 hours ago

[dead]

Comment by noelwelsh 4 hours ago

I thought "morsel-driven" was AI slop, but it turns out to be in common usage in the HPC world. So I learned something from this post!

Comment by tosh 3 hours ago

afaiu morsel-driven means the workload gets turned into 'smallish' chunks (morsels)

instead of having to pre-allocate upfront (e.g. 4 nodes get 1/4 each) it is more granular and dynamic

a worker that's "done" can request another morsel

pragmatic approach because nodes might not all be equally fast (cache, cpu frequency, throttling, …) and also some morsel workloads take longer than others depending on the values they contain and what kind of work needs to get done

so this approach tends to balance out nicely

I'm sure someone else can explain it better / correct me (please do!)

Comment by noelwelsh 2 hours ago

When I read up, it sounded like the same idea as work-stealing to me. Not surprising that different fields come up with the same idea under different terminology.

Comment by hetoku 3 hours ago

Exactly!

Comment by hetoku 3 hours ago

[flagged]