3 ms·
Just because it's using a web service doesn't mean the algorithm itself isn't running efficiently on hardware. I imagine you ship off the data, let them run th
by morgante 12y ago
Just because it's using a web service doesn't mean the algorithm itself isn't running efficiently on hardware.
I imagine you ship off the data, let them run the algorithm, and they return the results. This has no effect on the Big-O efficiency of the algorithm; the only additional cost is a simple roundtrip of the data.
I'm failing to see how that's so different from ex. running an intense algorithm in a worker thread.
- milge 12y agoI'm thinking back to some image processing processes I've implemented that had multiple algorithms. Passing images to a service like this back and forth would slow down those processes greatly. YMMV.
- jbarrow 12y agoThis would see a significant slowdown for any algorithm that requires large amounts of data, as a lot of them do. The core philosophy of Hadoop which made it successful was "move the computation to the data and not the other way around." Although the algorithms may run efficiently, ferrying significant amounts of data to and from a web service could quickly negate any gains.
- doppenhe 12y agoabsolutely agreed which is way in almost 80% of cases we ship the computation to the data by running in the same data centers where the data lives.