I mostly agree with this position. My idea is to collect as much information now so that I can investigate later on before is gone. I also need to know how to design the benchmarks so that they…
I will refer to the "system" userspace configuration as just userspace, and the environment that you get with a mix of nix develop and home manager as your environment.
Ok, makes sense,…
Given that only one CPU is initializing all the memory, I don't think that...
Yes, I agree with that analysis, with one CPU touching all memory it should be allocated on that CPU's NUMA node.…
As commented by Slack, I would say the difference between my results being faster is probably bc. in my benchmarks I use this instead of malloc:
void *tglib_mmap_wrapper(size_t length)…
About the parameters of cholesky: size 32*1024, tasksize 512 (the one with the bigger performance difference). Immediate successor was activated.
Important to note that in my version, I…
I have executed the cholesky before and after the upgrade. Results show some degrade, very noticeable with large tasksizes:
Tasksize 384 (best tasksize)
x after_384.out
+ before_384.out…
@rarias Can we delay the upgrade of fox until 17 of January? One day after the wamta deadline, turns out getting results never ends
(...) I think it should be safe to remove them? @varcila
We can try, I think it makes sense to remove them.
Thanks for the copy. FYI, I have finished most of the batch of jobs I needed to execute this year, so I will most probably not use Fox until the second of January when I come back from holidays.…
I can confirm that now I can ssh from other terminals from apex, and from my machine, with and without the --no-shell option.
I am having trouble loging into fox, I guess related to LaunchParameters=use_interactive_step:
This is from my machine:
Connection closed by 147.83.30.141 port 22
I can login…