Slashdot Mirror
Japan Unveils Next-Generation, Pascal-Based AI Supercomputer (nextplatform.com)
The Tokyo Institute of Technology has announced plans to launch Japan's "fastest AI supercomputer" this summer. The supercomputer is called Tsubame 3.0 and will use Nvidia's latest Pascal-based Tesla P100 GPU accelerators to double its performance over its predecessor, the Tsubame 2.5. Slashdot reader kipperstem77 shares an excerpt from a report via The Next Platform: With all of those CPUs and GPUs, Tsubame 3.0 will have 12.15 petaflops of peak double precision performance, and is rated at 24.3 petaflops single precision and, importantly, is rated at 47.2 petaflops at the half precision that is important for neural networks employed in deep learning applications. When added to the existing Tsubame 2.5 machine and the experimental immersion-cooled Tsubame-KFC system, TiTech will have a total of 6,720 GPUs to bring to bear on workloads, adding up to a total of 64.3 aggregate petaflops at half precision. (This is interesting to us because that means Nvidia has worked with TiTech to get half precision working on Kepler GPUs, which did not formally support half precision.)
Am I the only one that thought "LISP machines, okay, but Pascal?"
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
That is actually the first thing that sprang to mind, even though I had been looking specifically at Pascal based GPU's recently. :-)
"There is more worth loving than we have strength to love." - Brian Jay Stanley
These P100 come with sweet HBM2 and around 500GB/s in memory bandwidth... everything based on dense linear algebra (AI, but also physics simulations) is basically flying on them.
I'm sorry, but I like my KFC hot from the fryer. This experiment should end immediately.
I've fallen off your lawn, and I can't get up.
Kepler Fluid Cooled, though Tsubame is a kind of bird and the computers are indeed immersed in oil.
Also Japan has an unusual tradition of eating KFC for Christmas with reservations made months in advance.
For some reason, Kernel Sanders made me think of Dr Fun: Kernel Panic
For those that don't know, Dr Fun was the first webcomic 520 weeks, or 10 years worth
I had a pretty deep fondness for Pascal back in the day, and messed around with Delphi, Modula and Oberon, but the reality is that these aren't exactly common languages anymore, at least not in commercial circles. It's a real pity too, because learning TurboPascal was my sort of "Wizard of Oz black-and-white to color" moment back in highschool, where I shed all the evils that I had learned through mucking around with various flavors of BASIC, and basked in the glory of structured procedural code.
The world's burning. Moped Jesus spotted on I50. Details at 11.
I thought all Pascal use was for BBS DOOR games, and the internet killed it?
I am going to make make a supercomputer that runs on BASIC A.
Whom the gods would destroy, first they teach basic.
Pascal, the GPU design. Not Pascal, the language.
Now, if you'll excuse me, I have backups to corrupt.
You do not need to. Free Pascal is well and alive on multiple platforms and is open source. http://www.freepascal.org/
I think I'm one of few people that actual likes Pascal. Also prefer Python over JAVA and never really cared for C all that much even though there are similarities. Anyone like or use MyNotex (Linux)? Written in with Pascal. ;)
As of now there are very few applications for massively souped up GPU processes. Fluid mechanics loves this GPU. Navier-Stokes is probably the most difficult equation to solve, agreed. But it is hyperbolic, with limited "zone of influence", and numerical equations are quite simple, just mass, momentum and energy balances in the control volume. It plays well in GPU, the calculations fit inside the teensy memory and processor. All time domain problems are hyperbolic and they all can be ported to GPU, theoretically. But try squeezing Maxwell's Equations into that teensy processor!
Graphics card companies are desperately looking for new markets and they keep pushing this. They might as well push a wet noodle across the table. It ain't gonna go nowhere it didn't wanna go.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Making all the other supercomputers Wirth-less.
My spoon is too big.
One it was realized you could mechanically translate Pascal to C, then compile the C and get a 2-3x speed up (compared to interpreting p-code), Pascal started dying.
C has issues, but in practice it has less of them than Pascal, so the resulting code was easy to tweak to get even more performance.
Pascal usage quickly shrank. I'm not quite sure why, it was a fairly decent compiler-based language.
I am pretty sure why. More modern operating systems came up and nearly invariably they were all C based. If you wanted to call the OS libraries you were better off using C. That's why Pascal died off.
Delphi.. Ohhh such wonderful memories..
-The wise argue that there are few absolutes, the fool argues that there are no probabilities.
And you probably prefer your KFC to be chicken and not swallow, which is what Tsubame means.
And the first step to destroy the gods is to learn BASIC. The next step is to learn how to create and embed your own commands into a BASIC compiler. But tread carefully! The believers in the gods seek out those who would destroy the gods. A man named Steve McNeill, http://www.qb64.net/forum/inde... started down that path and was brought low, and a recent accounting of his tale was scrubbed from the annals of http://www.qb64.net/forum/inde...
It also allowed nesting of functions.
FWIW GCC allows that now in C.
"First they came for the slanderers and i said nothing."
Faster hardware is not always a boon. Now we have Java monsters that eat up all the performance of even decent hardware. Easy to learn? Nah, with the myriads of different libraries and paths it is a conceptual mess. And it was supposed to be the cure-all for viruses, but that has not materialized either.
The good Lord gave us C, Bash and the CLI , and we frail humans should not presume to improve on His creation.
Paai
It is good that I am an atheist, then.
"It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
Precisely so. Well played. :)
I've fallen off your lawn, and I can't get up.
You can call a C library or OS functiom from Pascal, too.
There is no difference.
C is not something magically, you know ...
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
Faster hardware is not always a boon. Now we have Java monsters that eat up all the performance of even decent hardware. Easy to learn? Nah, with the myriads of different libraries and paths it is a conceptual mess. And it was supposed to be the cure-all for viruses, but that has not materialized either.
The good Lord gave us C, Bash and the CLI , and we frail humans should not presume to improve on His creation.
Paai
Those are tools of the Devil; on the 1st day, the Lord created binary, microcode and logic gates and saw that it was good.
Pain is merely failure leaving the body
I don't know if there is any difference between calling conventions, but the mere fact you would have to write your own headers in Pascal seems pretty significant to me.
Ofc, there are different calling conventions.
Usually C pushes arguments from left to right onto the stack and the caller cleans up the stack (because of variable argument lists), in Pascal arguments get pushed from right to left and the called procedure/fuction cleans up the stack.
Interfacing with C you usually do via so called 'units'. Units have an interface section and an implementation section. In the interface section you define functions/procedures and call also define if they are written in a different language (Assembly, C, Fortran), unfortunately there is no standard how to do that exactly. (Implementation section would be empty and you have to link with the relevant C library, ofc.)
Most C compilers also used to support 'extern PASCAL' or 'extern FORTRAN' keywords/declarations. But again I think there is no standard for that.
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.