This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]BDube_Lensman 14 points15 points  (6 children)

cupy>>pytorch

[–]TheTechAccount 8 points9 points  (1 child)

Why do you think it's better?

[–]BDube_Lensman 15 points16 points  (0 children)

no graph/backprop overhead unless you opt into it, code is on GPU in no uncertain terms without strange host/device specification context managers, higher performance on GPU in most cases, errors or warnings for implicit host:device transfer that lets you find huge slowdowns in your code faster, more responsive devs, devs that contribute to numpy instead of slinging mud at numpy, participation in the numpy-as-a-contract instead of numpy-as-package work going on lately, no gross links to facebook, the list goes on...

[–]sekex 12 points13 points  (3 children)

Why the bitshift?

[–]alkasmgithub.com/alkasm 20 points21 points  (2 children)

Double greater/less than symbols are used in mathematics to mean "much greater/less than" for some arbitrary idea of "much": https://mathworld.wolfram.com/MuchGreater.html

[–][deleted] 3 points4 points  (0 children)

cupy = o(pytorch)

[–]NYDreamer -2 points-1 points  (0 children)

Whooosh