3 ms·
I didn't see any mention of striding. For convnets, you have to do a very unwieldy data unroll that either copies your data by (nxn) where n is the width of yo
by dnautics 10y ago
I didn't see any mention of striding. For convnets, you have to do a very unwieldy data unroll that either copies your data by (nxn) where n is the width of your kernel, or you have to manually stride, which can cause all sorts of problems with memory bank collisions, paging problems, etc.
- jacquesm 10y agoYes, this is a real problem. I can easily tell if my GPU is having striding issues by looking at the power consumption of the machine. If I manage to get > 40% utilization I consider that pretty good. GPUs are useful but far from perfect for this application and the quickest way to sink performance is to 'starve the beast' by having sub-optimal memory access patterns.
- deepnotderp 10y agoSo don't use a GPU, don't suffer from old paradigms :)
- radarsat1 10y agoCouldn't you organize the input data in a "pre-strided" layout? Not sure if that makes any sense.. But I mean, re-arrange the pixels so that consecutive pixels per stride are consecutive in memory.
- dnautics 10y ago> For convnets, you have to do a very unwieldy data unroll that either copies your data by (nxn) where n is the width of your kernel Justin does a WAY better job of explaining it than I do https://www.youtube.com/watch?v=dUTzeP_HTZg&t=36m30s https://www.youtube.com/watch?v=dUTzeP_HTZg&t=36m30s