gnufx

72 ms·

901.
by gnufx 6y ago
The Hot Chips piece mentioned has comparisons with both versions of SPARCfx as far as I remember.
902.
by gnufx 6y ago
I know, but it's different apart from coming in different hardware widths, as ARM techies will gush.
903.
by gnufx 6y ago
Sure, but people don't normally think of "GPU" in this context as just runs all your x86_64 code.
904.
by gnufx 6y ago
Perhaps it's worth pointing out some context. Given the remarkable predecessor, K Computer, this was only a matter of time. (I heard a great early talk on K, and I wish I knew the speaker for credit who was obviously working quite ha
905.
by gnufx 6y ago
I don't know whats the best reference, but here's one: https://www.fujitsu.com/global/Images/the-tofu-interconnect-...
906.
by gnufx 6y ago
Summit and Sierra, for instance, actually run a fair range of applications fast, though Sierra is probably targetted mainly at weapons simulation-type tasks. A typical HPC system for research, e.g. university or regional, has to be pretty
907.
by gnufx 6y ago
If you want to understand distributed-memory parallel performance you're probably better off with a simulator, like SimGrid. I don't know what bog-standard hardware you'd need to get a typical correct balance between floatin
908.
by gnufx 6y ago
I haven't checked the current list, but previous ones have been roughly half "cloud provider" systems with essentially useless interconnects for real HPC work. NCSA refused to indulge in the game with Blue Waters, notably.
909.
by gnufx 6y ago
I'm not sure what predecessors that means (ThunderX2?), but these have been carefully "co-designed" for the job with experience from K Computer. Actually that's for a set of job types, which is part of the point. They a
910.
by gnufx 6y ago
(SVE isn't 512-bit SIMD like AVX512.) I don't know what BLAS they're using, though I know they've long worked on their own, but BLIS has gained SVE support recently, for what it's worth.
911.
by gnufx 6y ago
As an early user of KNL, I don't get the "GPU" bit. KNL runs normal x86_64 code and doesn't look that much different to the AMD Interlagos systems I once used apart from the memory architecture.
912.
by gnufx 6y ago
I'm pretty sure there's an emulator, which is how you usually do early development.
913.
by gnufx 6y ago
This seems to be claiming that virtual memory wasn't invented -- or at least first implemented -- at Manchester for ATLAS. Is there justification for that, as opposed to when it was first commercially available or in service?
914.
by gnufx 6y ago
Changing uids is something you don't want for HPC use anyhow. Charliecloud is a simple alternative approach specifically for HPC. Actually, a lot of the time you can get away without namespacing anyhow, just by settings paths to point
915.
by gnufx 6y ago
Lack of CVEs for security issues is part of the problem with it. I think SUSE rejected it on the basis of auditing. While it would be better to run a capability micro-kernel-ish system, you're stuck with Linux for things like HPC. The
916.
by gnufx 6y ago
Yes, but if you were serious about espionage, say, you wouldn't draw attention to the compromise by running one.
917.
by gnufx 6y ago
Yes, the fundamental problem is that this sort of thing has around the top of the threat list for academic computing facilities for 30 years or so (originally typically coming in to the UK from CERN). It's just that this is larger sca
918.
by gnufx 6y ago
If I'm programming in Lisp, I actually want the same venerable Lisp-based IDE that I use for other languages.
919.
by gnufx 6y ago
I don't recognise the picture of Lisp programming qua Lisp. "Refactor" probably wasn't even a word you'd hear for most of Lisp's existence. The Common Lisp standard definition is clearly not churning. I used
920.
by gnufx 6y ago
Latter-day Dylan is infix with a Scheme-y macro system: https://opendylan.org/books/dpg/macros.html Cue arguments, I guess, about whether Scheme is a Lisp, whatever their standards say.
921.
by gnufx 6y ago
I don't remember ever hearing of Ralph when Dylan appeared, though that was long ago. Was it talked about externally?
922.
by gnufx 6y ago
Dylan originally used Lisp syntax, as documented in the Dylan Manual; there was angst when it changed. I don't have that with me, but it's online: http://lispm.de/docs/prefix-dylan/book.annotated/
923.
by gnufx 6y ago
Perhaps we should let them know they're too predictable! (Ross Anderson rightly ranted on the topic somewhere.)
924.
by gnufx 6y ago
New to me, but it was suggestive somehow of Mitchell and Web before watching it.
925.
by gnufx 6y ago
It's existed for a fair while as Infiniband doing Linux by-pass; the comment didn't say TCP/IP. (The general technique pre-dates Linux, of course.)
926.
by gnufx 6y ago
One take, from Robin Popplestone, long ago in comp.lang.functional: “… it does seem to me that … OOP represents the discovery by the mainstream community that it is a good idea to associate code with data, but, since they still don't k
927.
by gnufx 6y ago
Experimentally, you don't need luck to set up ~200 dedicated hardware nodes in minutes in an HPC cluster, for instance. (They do have to be connected up, with known or discoverable MAC addresses.)
928.
by gnufx 6y ago
Are those kernel bypasses better than the Linux-based RDMA we've had for ages (on appropriate fabrics)?
929.
by gnufx 6y ago
Whatever the reason, people shouldn't be propagating the incorrect information, especially if they're in research, and if they're interested in performance, which requires measurements. The same thing needs saying over and ov
930.
by gnufx 6y ago
I'm not surprised expecting to beat implementations of the basic Goto strategy for BLAS didn't turn out well. BLIS only needs a single, pared-down GEMM kernel for level3, and maybe one for TRSM. (It doesn't currently have G

More ›