tgamblin

13 ms·

91.
Runners that run as you: Gitlab CI for multi-tenant HPC(onyxpoint.com)
2 points by tgamblin 8y ago|0 comments
92.
Secure setuid runners for GitLab(onyxpoint.com)
3 points by tgamblin 8y ago|0 comments
93.
by tgamblin 8y ago
In what sense? The ranking is still based on LINPACK scores, and it's intended to represent the fastest machines for scientific computing. We can argue about whether modern simulation codes look like LINPACK (they don't) but ne
94.
by tgamblin 9y ago
There are plenty of scientific and engineering fluid dynamics codes that take advantage of GPUs. The current fastest supercomputer in the US, Titan at ORNL, uses GPUs. Here’s a CFD code that ran on it: https://www.olcf.ornl.gov&
95.
by tgamblin 9y ago
If you're talking about MPI and its use in HPC, you might've been mostly correct 5 years ago. Now, HPC applications at the largest sites are hybrid MPI+OpenMP (or some other threading model, or they use GPUs). On Xeon Phi system
96.
by tgamblin 9y ago
It's not yet the production tool that Homebrew is, but there is Spack: https://spack.io , which allows installing arbitrarily many builds of a package, with different versions, compilers, and options (disclaimer: I'm th
97.
LLNL rescues nuclear test footage, posts 64 declassified films on YouTube(llnl.gov)
10 points by tgamblin 10y ago|0 comments
98.
by tgamblin 10y ago
Another place this use case comes up is supercomputing. Not because of the unusual levels of radioactivity, but because of unusual numbers of processors. When you have more components, a single bit flip somewhere is increasingly likely.
99.
by tgamblin 11y ago
I manage my dotfiles in a separate git repo in ~/.dotfiles, and I have simple scripts that link and unlink everything. It's worked well for me for quite some time: https://github.com/tgamblin/dotfiles
100.
by tgamblin 11y ago
The common complaint about stackoverflow reputation is that it's a function of the number of questions answered and not actual skill. http://stackrating.com/ gives an Elo rating of stackoverflow users, where you'r
101.
by tgamblin 11y ago
In Spack this would look like: spack install guis ^guile@<new version> How do you handle optional dependencies in this model? Or, a more complex case, dependencies that are only present for certain versions of the package?
102.
by tgamblin 11y ago
These are the things that Spack attempts to solve. If you look at slides 14-15 in the presentation above, the concretization process automates something like your second example. You can build with an arbitrary package version, e.g. `spa
103.
by tgamblin 11y ago
My point is mainly that the package specification in Guix is very verbose -- I must hack (and in some cases generate) package files to do what I want to do. The approaches you mention for generating package variants seem to generate new pa
104.
by tgamblin 11y ago
How does this work security-wise? Can any user deploy on your clusters? AFAIK Guix requires root/chroot. This would never fly at our site...
105.
by tgamblin 11y ago
> The novel idea in functional package management is that a package can be viewed as a pure function whose arguments are the dependencies, the source code, the build script, etc. and whose output is the built binary. And this is an aweso
106.
by tgamblin 11y ago
Spack has, to some degree, a compromise between the language and system package management sides of things. Languages in Spack can specify how their extensions should be activated/deactivated within the installation, and modules like
107.
by tgamblin 11y ago
Got to agree with davexunit here. Language package managers aren't going to handle your non-<language> dependencies. One place where this comes up in spades is with numerical software. Example: frequently you want to build num
108.
by tgamblin 11y ago
It's intercepting system calls with ptrace, so it could easily fool the process into thinking its calls did exactly what was expected. A cursory glance through the code indicates that it mostly does. However, it looks like it doesn&#x2
109.
by tgamblin 11y ago
Spack [1,2] is our attempt to do this for HPC, where we have two things going on: 1) Our applications aren't single-language. They include Fortran, Python, C, C++, Yorick (!), Lua, etc. etc. 2) We have a major combinatorial versioning