4 ms·
> Rust offers much lower TCO Just to satisfy my curiosity, since I’m not that familiar with distributed computing, how is tail call optimization relevant in t
by hellofunk 7y ago
> Rust offers much lower TCO
Just to satisfy my curiosity, since I’m not that familiar with distributed computing, how is tail call optimization relevant in this area?
- ohnoesjmr 7y agoIt's total cost of ownership. Spark is a beast, half the resources is taken up by the platform itself.
- matteuan 7y agoReally? Can you explain better "half the resources is taken up by the platform itself". Do you have some numbers, experiments?
- ohnoesjmr 7y agoRunning hadoop nodes, name nodes, yarn masters. These are massive complicated processes, that cumulatively are usually more complicated and expensive than the spark jobs themselves. At least from the cases I've seen.
- liancheng 7y agoActually, none of these processes is essential for running Spark unless you have to read data from HDFS and have to run Spark on YARN. Spark supports reading data from different sources, e.g., cloud blob storage, relational databases, NoSQL systems like C* and HBase. NameNode is only required if your data is stored on HDFS, and that is not an essential problem of Spark. As for scheduling, Spark can run in standalone mode without any YARN components. Actually, that is how Spark clusters run in Databricks.