This walkthrough is planned but not published yet. The transcript below covers the same material if you would rather read it now.
Which array operations Eugo moves to the GPU on its own, and how to confirm it happened.
Eugo inspects the operations in your code and moves computationally intensive array work onto a GPU when one is available and the transfer is worth paying for. Large matrix multiplications and elementwise operations over big arrays are good candidates. Small arrays are not: copying to device memory and back costs more than the operation saves. You do not annotate anything, but you should verify. Check the run summary to see where work actually executed.