由网友(疯癫阔少爷)分享简介：什么是最成熟的.NET MPI实现？快速谷歌搜索变成了两个下方，但我不熟悉其中任何一个。我认为，第一项（mpi.net）是基于微软MPI 的。有什么想法？What is the most mature .NET MPI implementation? A quick google search turned up t...

什么是最成熟的.NET MPI实现？快速谷歌搜索变成了两个下方，但我不熟悉其中任何一个。我认为，第一项（mpi.net）是基于微软MPI 的。有什么想法？

What is the most mature .NET MPI implementation? A quick google search turned up the two below, but I'm not familiar with either of them. I believe the first item (mpi.net) is based on Microsoft MPI. Any thoughts?

http://www.osl.iu.edu/research/mpi.net /

http://www.purempi.net/

推荐答案

的 MPI.NET的常见问题解答说：

在Unix上，然而，MPI.NET自适应于本地MPI在配置时检测到，并可与工作（至少）打开MPI，LAM / MPI和MPICH2。

On Unix, however, MPI.NET adapts itself to the native MPI detected at configure time, and can work with (at least) Open MPI, LAM/MPI, and MPICH2.

虽然在Windows上这似乎是一个完全托管的解决方案。 AFAICT，纯Mpi.NET只是一个托管解决方案。

although on Windows it appears to be a completely managed solution. AFAICT, Pure Mpi.NET is only a managed solution.

我还没有使用任何这些实现​​的 - 事实上，它已经有一段时间，因为我用的任意的MPI - 但我会怀疑MPI.NET具有较高的可能性整体的稳定性，因为它实际可用时使用尝试和真正的Unix实现。那些Unix实现已经在该领域进行更长的时间，因此，一般不太可能是马车 - 或者至少如果有错误，他们很可能是公知的由现在

I haven't used either of these implementations -- in fact, it's been a while since I've used any MPI -- but I would suspect that MPI.NET has a higher likelihood of overall stability since it will actually use the "tried-and-true" Unix implementations when available. Those Unix implementations have been in the field for a much longer time, and as such are generally less likely to be buggy -- or at least if there are bugs, they are probably well-known by now.