Earlier quoted context omitted.
Ok, so that's 6.4 cores per mm^2 while Kepler has 4.8. Not bad, considering NVIDIA has already shrunk the scheduling ressources, register blocks and cache sizes per core to a bare minimum (something I don't agree with btw.).
What do you consider a Kepler core? The Epiphany cores are dual issue RISC processors that run independent C/C++ tasks.
Parallella: A Supercomputer For Everyone
61–70 of 89 posts
Re: Parallella: A Supercomputer For Everyone
#62Earlier quoted context omitted.
Sure, you're limited by money. But if someone magically was able to produce a machine for $100 that was on par with Titan ( http://en.wikipedia.org/wiki/Titan_(supercomputer) ) I would still call it a "supercomputer" until it became ubiquitous.
If they only had one, it doesn't matter how much it cost them to make, it's worth much much more than $100 dollars to someone. If there were enough supply that it were possible for it to be only $100 then it would have to already be ubiquitous. I agree with jacques_chester that it's an economic distinction.
I agree that you're not going to get a "supercomputer" for less than about $100,000. But supercomputers are defined by what they can do. Their cost is secondary. Necessary in a world without magic, but secondary. I can spend $100,000 on a computer, but that alone does not make it a "supercomputer".
Re: Parallella: A Supercomputer For Everyone
#63Earlier quoted context omitted.
Very good way of summing it up!
Yes, agreed! We definitely got carried away with the marketing lingo and we apologize! This was our thought process: We have received a lot of negative feedback regarding this number so we want to explain the meaning and motivation. A single number can never characterize the performance of an architecture. The only thing that really matters is how many seconds and how many joules YOUR application consumes on a specif…
That said, I still think that the GHz stat is just about as BAD a metric as any (I suppose "pin count times # of cores" would be worse :-). About the only positive inference I can draw from this is that you have the thermal situation in your system under control.
But piling up cores and cooling them is, IMHO, one of the easiest parts of designing a massively parallel system. The interesting part of the design is the interconnections between the cores, and any metric that multiplies single core performance by number of cores tells me nothing about that.
So not only am I not learning a key part of the performance characteristics of your system, but by omitting it, you make me wonder whether the ENGINEERING of the system might be similarly misguided on this aspect as the MARKETING seems to be (i.e. does marketing omit this aspect of the system because it was not important to the engineers either?).
Linpack at least has benchmarks both for showing off the cores in nearly independent scenarios, and for showing the system when actual communication has to take place. Obviously, each parallel application is different, but you'd at least show ONE indication of performance in situations that are not embarrassingly parallel (http://en.wikipedia.org/wiki/Embarrassingly_parallel).
Re: Parallella: A Supercomputer For Everyone
#64Does anyone know what kind of cores these RISC cores will be? Will it be some lower end ARM version, or MIPS? Will it be something for which a wide array of tooling already exists, or will this have its own custom architecture which only works with their toolchain?
According to the kickstarter page the RISC cores are ARM A9.
Re: Parallella: A Supercomputer For Everyone
#65I picked up a raspberry Pi a few days ago. Initially, I was blown away by the low price point. Since then, I've been reflecting on what makes a computer useful. For personal computers - desktops and laptops - I think we don't have a shortage of processor cycles. The minimal specs of the Raspberry Pi make it useable - 256MB of RAM, 700 MHz CPU, a few GB of storage and enough MB to saturate a home broadband connection.…
That plus cheap access to a massively parallel computer could also be very interesting.
Except where raspberry Pi + online storage could be useful to many, many people. Massive parallelism is probably only interesting to folks like us.
Re: Parallella: A Supercomputer For Everyone
#66Earlier quoted context omitted.
What do you consider a Kepler core? The Epiphany cores are dual issue RISC processors that run independent C/C++ tasks.
Kepler has 8 "SMX" with 196 parallel sp threads each. For me the number of cores = the number of parallel threads, although on GPU they are not as independent, i.e. each "core" of an SMX either executes the same instruction on adjacent data or does nop. With dual issue do you mean a two stage pipeline or two threads in parallel, both performing FLOP?
Re: Parallella: A Supercomputer For Everyone
#67If the Kickstarter falls through, what options could you still make available to hobbyists? Is there some version of your current prototype setup that you could sell, even if it's not one convenient board?
Re: Parallella: A Supercomputer For Everyone
#68Earlier quoted context omitted.
I don't think a $2.35M round is really that much for a chip startup. The fact that they even think that they can plausibly launch a chip and some level of supporting documentation, software, etc for ~$3M total, that is a remarkably efficient use of funds. By the way, Kickstarter funds are "cheap" (no dilution & no debt) so anyone who can actually raise money on Kickstarter should do so.
I'm not qualified to evaluate how much money a modern chip startup needs to launch a product. But it's worth noting that the Kickstarter pitch doesn't mention the millions the company has raised so far (apologies if I missed that part). >> Kickstarter funds are "cheap" (no dilution & no debt) Of course they are, and that's kind of my point. Raising money from unsophisticated unaccredited investors without providing f…
Re: Parallella: A Supercomputer For Everyone
#69And if it is so, should expecting Erlang compiler be out of the question? :)
Re: Parallella: A Supercomputer For Everyone
#70What's the point in having such a RAM/core ratio? By assigning 4 threads per core (which is fairly common to exploit manycore architectures) you don't even have 4Meg of memory per thread. I would totally agree that memory constraint is sort of tied to manycore architectures, but in this case I find it pushed to the limits.