outrun
icecream
outrun | icecream | |
---|---|---|
13 | 16 | |
3,109 | 1,553 | |
- | 0.6% | |
0.0 | 0.0 | |
over 1 year ago | 5 months ago | |
Python | C++ | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
outrun
-
Distcc: A fast, free distributed C/C++ compiler
While it's purpose is different it can be used to do distributed compiling, so I'll leave it here.
https://github.com/Overv/outrun
Since I was just going down this rabbit hole recently, I kind of wonder if it's possible to set the filesystem on something more like the BitTorrent protocol so things like the libraries/compilers/headers that are used during compilation dont all need to come from the main pc. It probably wouldn't be useful until you reached a stupid number of computers and you started reaching the limits of the Ethernet wire, but for something stupid that can run on a pi cluster it would be a fun project.
-
Programing laptop
Your mention of compile heavy workloads reminded me of a project called Outrun, it offloads work to another machine. All it seems to require is Python, Fuse3 and ssh.
-
The u-root CPU command
Awesome! This write up is satisfyingly detailed. Prior work in this space includes Plan9 of course, as well as the python project Outrun, which has it's own RPC-based FUSE FS: https://github.com/Overv/outrun
Other approachs to deployment in particular include the functional package managers Nix and Guix, which can create lightweight application images, and could probably be cobbled together into some sort of remote environment replication even across architectures. As I read on, I thought less about how this compares with Guix in regards to application/environment packaging and more about how these things could be glued together in interesting ways, because I think the intro leads in through slightly off-label examples, if that makes sense. Application packaging isn't what this addresses at the end of the day, but it's no less fascinating for it.
- GitHub - Overv/outrun: Execute a local command using the processing power of another Linux machine.
- Way to run commands using other linux system's compute power
- Outrun - Execute a local command using the processing power of another Linux machine.
icecream
- Icecream: Distributed compiler with a central scheduler to share build load
-
Distcc: A fast, free distributed C/C++ compiler
Related
https://github.com/icecc/icecream - another option that does what distcc does, but aimed at a somewhat different use case.
https://ccache.dev/ - a similar idea but provides caching of build outputs instead of distributing builds. You can use it together with distcc to achieve even better performance.
-
Do you use ccache to speed up compilation times
Of course! The github readme provides a lot of info - https://github.com/icecc/icecream
- GitHub - icecc/icecream: Distributed compiler with a central scheduler to share build load
-
Ccache – a fast C/C++ compiler cache
If you like distcc, did you ever give icecc a try?
https://github.com/icecc/icecream
I never had the time to set it up properly, but by the looks of it, it should be even better.
- People who use distributed builds, how do you handle many compilers?
- Fuchsia Workstation
-
Give local devices a way to connect to clients? - openvpn
I would like to have a icecc setup I can vpn into. It seems that with normal configs the clients can talk to the scheduler, but the scheduler cant connect to the clients as it tries to connect to the device running the openvpn server not the one behind it. How could I make my openvpn clients appear almost as physical devices on the network, with unique IP's that local devices can connect to; or if that is unnecessary how could I solve this?
-
ccache 4.6 released
Glad to see a new release on this! I've read worrying news about the state of icecc, and the followup uncertain news on sccache, so I hope at least some part of the tooling is in a good shape.
-
Best way to manage dependencies with c++?
I always wanted to try to use cmake-conan so I could let Conan grab all packages but have a neat cmake script being in charge of what gets built when. Also, this would allow me to easily switch between CMake fetchcontent and Conan packages that may or may not be stashed automatically on a local Artifactory server. Secondly, since now all build requirements are stashed on a server and binary reproducible, you could concider adding icecream and ccache into the mix. (Try running a node one of your buildservers for massive speadups with icecream) This however does require a reproducible build environment (by configure script) which conan again is really good in.
What are some alternatives?
rffmpeg - rffmpeg: remote SSH FFmpeg wrapper tool
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
OpenAFS - Fork of OpenAFS from git.openafs.org for visualization
ccache - ccache – a fast compiler cache
llama
keppel - Regionally federated multi-tenant container image registry
cargo-mutants - :zombie: Inject bugs and see if your tests catch them!
compiler-benchmark - Benchmarks compilation speeds of different combinations of languages and compilers.
remote-apis - An API for caching and execution of actions on a remote system.
gg - The Stanford Builder
bazel-buildfarm - Bazel remote caching and execution service
cmake-init-conan-example - cmake-init generated executable project with Conan integration