Hi Ward, *,
On Nov 4, 2013, at 8:15 PM, Ward Poelmans wrote:
>> * module statistics! # how to record module usage; what do you do?
>
> Is this something for EB? I would think it's more something to
> implement in lmod?
It is more of a survey to fellows about what they do, so that we can do some
shopping;
I found out that TACC checks env during shell logout, while UGhent rewires
module() cmd.
>> * Inform upstream developers of patch effort, add REF. with tracking URL
>> within patch files
>
> +1, I usually push patches upstream but something to add tracking
> would be useful.
Indeed, eventually we would all benefit more by showing to the upstream
developers,
any hacks we need to apply to get things done - for an HPC service; in my
experience,
most care about it and will eventually fix it or, provide hooks to avoid
patching.
>> * diverse build regtest environment, ensure multiple OSes/archs/distros
>> tested
>
> Isn't this something that a bunch of vm's would solve?
Except for ATLAS (goalf) and other such auto-tuning software, VMs will do fine
for x86;
things get more tricky though, if you start considering other architectures.
Now that I recall about it, even classic FFTW has some short of auto-tuning...
"wisdom";
if performance level is part of the regtest... go figure.
cheers,
Fotis
--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
| sed 's/better bash/bash better/' # Yelling in a CERN forum
