• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Algorithms not suited for mapreduce

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi there,

I would like to know a few algorithms that are not well suited for mapreduce and why they are not suited. I read, that svm is one of those algorithms but I don't know why.

Greetings, Andre
 
Bartender
Posts: 2407
36
Scala Python Oracle Postgres Database Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Not sure about specific algorithms, but map-reduce is probably most useful when you can run the map tasks independently in parallel. But if each task depends on output from another task, then you can't run them in parallel. So it will depend on how far you can break your job up into these parallel tasks or successive map-reduce steps. But you could explore ways to use higher-level tools - Hive, Cascading etc - which might allow you to define your task at a higher level and let the tools work out how to map-reduce it.
reply
    Bookmark Topic Watch Topic
  • New Topic