Spark streaming is a very different animal than Storm in that it does micro-batching rather than true streaming.
This has positives and negatives. Average latency on record by record processing will appear to be abysmal compared to Storm. Throughput could well be much higher because of the inherent batching. Failure tolerance will also be inherently better than raw Storm because the input is persisted and any batch can be replayed. The net is that a true head-to-head in any of these areas is likely to tilt massively toward one product or the other. On Mon, May 12, 2014 at 7:43 AM, Cody A. Ray <[email protected]> wrote: > I don't know of any head-to-head comparison, but I've never looked for one > either. I'm not very familiar with spark in general, but maybe someone else > on this list is? :) > > -Cody > On May 11, 2014 2:46 PM, "Weide Zhang" <[email protected]> wrote: > >> Hi Cody, >> >> Thanks for your reply. Do you know if there is any performance test >> result on Trident on throughput versus spark streaming ? According to the >> spark streaming paper, it claims to achieve better throughput than storm >> but I'm not sure if there is some insights why from storm community ? >> >> >> On Sun, May 11, 2014 at 11:13 AM, Cody A. Ray <[email protected]>wrote: >> >>> Have you read these? >>> >>> https://github.com/nathanmarz/storm/wiki/Trident-tutorial >>> >>> https://github.com/nathanmarz/storm/wiki/Trident-state >>> >>> -Cody >>> >>> >>> On Mon, May 5, 2014 at 6:38 PM, Sid Kiblawi <[email protected]> wrote: >>> >>>> I'm also interested in seeing some documentation on how trident >>>> implements this. Any help would be appreciated. >>>> >>>> -Sid >>>> >>>> On 05/04/14, Weide Zhang wrote: >>>> > Hi , >>>> > >>>> > Do you know if there is a good documentation on how trident implement >>>> exact once semantic ? Is there any performance trade off on using trident >>>> on achieving exact once semantic. How does trident performance compared >>>> with spark streaming ? >>>> > >>>> > >>>> > Thanks a lot, >>>> > >>>> > >>>> > Weide >>>> >>> >>> >>> >>> -- >>> Cody A. Ray, LEED AP >>> [email protected] >>> 215.501.7891 >>> >> >>
