使用 .Net 框架解决分布式计算问题的方法
我对编写一个项目感兴趣，该项目将某些计算分布在多台计算机上的大文件上。对分布式计算的需求源于我用来进行实际计算的软件的崩溃和不稳定性质 - 因此它可能会在某些计算机上崩溃，但其他计算机肯定会完成这项工作。 到目前为止我的想法包括： -使用多个服务器，每个服务器尽可能从主服务器中提取任务 -使用VMware -使用负载平衡集群
什么更适合这项工作？我还应该注意其他任何想法吗？
另外，如果您能推荐任何可靠的分布式计算C#框架，那将会很有帮助。
Im interested in programming a Project which distributes a certain computation on large files throughout several computers. The need for distributed computing arises from the crashy and unstable nature of the software I'm using to do the actual computing - so it might crash on some computers but others will surely do the job.
The ideas I have so far Include:
-Using several servers, each pulling a task from a master server whenever its possible
-Using VMwares
-Using a load-balancing Cluster
What is more suited for the job? Any other ideas I should be aware of?
Also, If you can recommend any reliable distributed computing C# framework, it will be helpful.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我自己还没有使用过其中任何一个，但我添加了书签 这个不久前就提出过这个问题。那里有一些好的建议。
haven't used any of these myself (yet), but I bookmarked this question a little while ago. some good suggestions there.
您看过 Hadoop MapReduce 吗？它是 Google MapReduce 框架的开源实现。虽然它是 Java 而不是 C#，但听起来它可能非常适合您的场景；主服务器自动处理分布式环境中的负载平衡和容错。
Have you looked at Hadoop MapReduce? It's an open-source implementation of Google's MapReduce framework. Though it's Java and not C#, it sounds like it could be perfectly suited to your scenario; the master server automatically handles load balancing and fault-tolerance in a distributed environment.
我会查看Appistry CloudIQ Platform。它将多台机器连接到一个由统一地址标识的计算框架中。您的客户端只需将作业提交到统一地址，框架就会将作业分发到各个机器上。它还监视任务执行，并可以自动重新启动失败的作业。因此，如果您的应用程序容易崩溃，那么这个框架可能是理想的选择。不要将相同的作业提交到多台机器（并浪费 CPU）来覆盖失败情况，只需提交一次，然后让框架处理重新启动实际失败的作业。我认为它非常适合您的可靠性问题。
I would check out Appistry CloudIQ Platform. It links together multiple machines into a single computing framework identified by a unified address. Your client simply submits jobs to the unified address, and the framework distributes jobs to individual machines. It also monitors task execution, and can automatically restart failed jobs. So if your application is prone to crashing, this framework could be ideal. Rather than submitting the same job to multiple machines (and wasting CPU) to cover the failure case, just submit it once, and let the framework handle restarting the jobs that actually fail. I would consider it ideal for your reliability concerns.