2 ms·
Worth noting it's ~100-lines of Go code that's quite readable: https://github.com/n7olkachev/imgdiff/blob/master/pkg/imgdiff/imgdiff.go https://github.com/n7ol
by alpb 6y ago
Worth noting it's ~100-lines of Go code that's quite readable:
https://github.com/n7olkachev/imgdiff/blob/master/pkg/imgdiff/imgdiff.go https://github.com/n7olkachev/imgdiff/blob/master/pkg/imgdif...
https://github.com/n7olkachev/imgdiff/blob/master/pkg/yiq/delta.go https://github.com/n7olkachev/imgdiff/blob/master/pkg/yiq/de...
- ganstyles 6y agoThis is a go question but I thought go funcs took less than a thread. This assigns one go func per cpu. Can it be faster with more go funcs per cpu?
- alpb 6y agoLikely not. Green threads concept (goroutines) makes a lot of sense if you block on I/O (such as reading DB, making RPCs), you can multiplex a thread. However, in this case, there is not a lot of I/O involved so regular CPU-bound parallel programming practices apply.