gloo
Collective communications library with various primitives for multi-machine training. (by facebookincubator)
why-ignite
Why should we use PyTorch-Ignite ? (by sdesrozis)
gloo | why-ignite | |
---|---|---|
2 | 1 | |
1,140 | 4 | |
0.7% | - | |
8.0 | 0.0 | |
6 days ago | almost 3 years ago | |
C++ | Python | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gloo
Posts with mentions or reviews of gloo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-24.
-
Releasing Gloo 0.4.0
These are two separate libraries that do very different things but share the same name. They are also written in two separate languages. That is a sizable gap between them, and reusing names happens often with libraries. Gloo (rust-wasm, this post) is also not new. Though, relative to Gloo (Go, solo-io), it is newer. But, there is also a Github repo even older than Gloo (solo-io): https://github.com/facebookincubator/gloo. As well, even if these were for some odd reason all about wasm, none of them are actually that popular. solo-io Gloo has the most stars (though that isn't the best metric of popularity, since it is relative to the community that actually uses it), but 3k simply isn't that much. There is certainly a good argument to look down on libraries that reuse popular library names, but this isn't really the case here. Both started not too long after each other (solo-io would not have most of the stars it currently has when Gloo-Rust started), are in separate languages (thus separate communities), and do very separate things.
-
Distributed Training Made Easy with PyTorch-Ignite
backends from native torch distributed configuration: nccl, gloo, mpi.
why-ignite
Posts with mentions or reviews of why-ignite.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-10.
-
Distributed Training Made Easy with PyTorch-Ignite
More information on launchers experiments can be found here.
What are some alternatives?
When comparing gloo and why-ignite you can also consider the following projects:
NCCL - Optimized primitives for collective multi-GPU communication
xla - Enabling PyTorch on XLA Devices (e.g. Google TPU)
ompi - Open MPI main development repository
gloo - The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
ignite - High-level library to help with training and evaluating neural networks in PyTorch flexibly and transparently.
idist-snippets