|
|
|
|
|
|
by matylla
2426 days ago
|
|
|
Sure, you could use a solution that simply wraps ImageMagick with a Ruby API and call is a day. The whole point of having a GPU-powered platform is processing speed. On average, it takes us 60ms to perform any stack of image transforming operations. That also benefits our users (who likes slows APIs?). With Metal Performance Shaders we have absolute control over pixels and direct access to the underlying hardware. For us that means we can rapidly test and deploy new CoreML models and also the ability to quickly respond to any feature-request. |
|
|
So this was my point in bringing it up: "We're faster than the other APIs out there" is a much more direct benefit to communicate to me as an API user than "We use GPUs, which makes us fast, faster than the competition, who don't use GPUs". The latter version has me making assumptions and eventually getting to a conclusion that matters to me; why not take me there immediately?
The thing is, as a non-expert in this area, I don't even fully understand whether the real performance bottleneck in such an API is the latency of uploading the image and downloading the result, or the computational processing of the image. So if using GPUs cuts the overall request time by 70%, that's great! If it only affects the round-trip time by 5%, then it's not a huge deal to me. As the domain expert, I'm relying on Pixaven's marketing to educate me on this.