I think uBeam is another Theranos, but granted at a much smaller scale. Still can't believe it has raised so much money and so much press without basic questions really being answered.
1,536 karma · joined March 14, 2011
2013 Thiel Fellow
2023-Present Positron AI (https://positron.ai)
2021-2023 Groq (https://groq.com)
2019-2020 Lambda Labs (http://lambdalabs.com); Managing hardware development and cloud/datacenter deployment
2013-2018 REX Computing(http://rexcomputing.com); Developed new processor architecture from scratch
@trsohmers
Follow me on twitter... @trsohmers
I think uBeam is another Theranos, but granted at a much smaller scale. Still can't believe it has raised so much money and so much press without basic questions really being answered.
Of course, I think that this is extremely impractical so it isn't a decision that I actually have to face. In this hypothetical scenario though, I'd much rather use the "transporter" as a cloning machine... having two of me would be pretty awesome.
I would definitely say I am socially awkward/inept, but I don't think that necessarily correlates with being socially maladapted/unaware of societies norms. The sort of "bro" culture that exemplifies UploadVR's, Uber, and many other "hot" tech companies right now is the culture that myself and most other high-school nerds that I knew rejected... we were not the popular kids that drank, had sex, and partied. I think all of this is a symptom of technology being a much more attractive jobspace for the general public (which includes a lot of "bros") compared to just for "nerds" that it was decades ago, and your conclusion is the exact opposite of this.
Granted it is an anecdote with a relatively small sample size, but I have not seen this sort of behavior/ideas from anyone who never went to college or dropped out, but I see it from plenty of folks in their late 20s/early 30s that never grew up from their college fraternity experiences.
As for upstreaming, it is something that we want to do, but are not sure if it will be accepted as our chip is not generally available at the moment. It would probably be done around the same time as our next tape out (which would be in larger quantity than our first one) when we would have generally available development kits this coming winter.
I have been working on public documentation in my spare time... originally supposed to go out in March but we have had other priorities. If you watch my Stanford talk I show the basic ISA overview as well as the WIP documentation made using doxygen. I'm hoping to get stuff out on our website before our next media push in ~June.
LLVM also has a bunch of awesome projects like Poly for polyhedral compilation that we are able to use that don't exist at all for GCC, or are very difficult to integrate. LLVMs lego block like architecture (it was originally designed as a tool to help build toolchains) plus things like Tablegen enabled our single "real" software engineer/CTO to do initial bring up of a backend in under a month.
These are the same reasons why DSPs have been VLIW since the 90s, and our initial applications overlap a lot. It has been sad to see the trend of TI and other DSP makers going down the path of adding hardware caching (that reduces determinism and energy efficiency) to try to "make it easier for programmers" when they already have a decent enough architecture, but a lack of good compiler tools to take advantage of it.
VLIW has gotten an extremely bad rap outside of the embedded space due to Itanium, which I strongly contend was not a VLIW in spirit (which you cans see me talk in more depth on here: https://youtu.be/ki6jVXZM2XU?t=441). Itanium introduced a ton of indeterminism by having static scheduling unfriendly things like branch prediction, variable latency caches, and still trying to have some level of support for x86. The core problem for Itanium is that it was impossible for the compiler to make good decisions in the vast majority of applications since the compiler could not know exactly where and when things in memory would be. I believe the underlying failure point has been computer architects for failed VLIW architectures not realizing that fancy bells and whistles and "cleverly complex" hardware designs is the exact opposite of what you want when the compiler needs to be able to do purely static allocation. Adding fancy dynamic pieces in hardware to account from this (seen in a lot of places with Itanium) just makes the problem worse.
The main improvement we have made with the Neo architecture is we have hard (exact cycle count) guarantees on all memory movements on and off the chip, which actually gives the compiler the information it needs to make good decisions and very condensed code. I think the jury is out on the applicability for "general purpose" code on VLIWs... it is not something we at REX really care about at the moment, and I think RISC-V is a great solution with improvements over x86 and ARM.
Not true, it is closer to 2 to 3x, and it is (slowly) getting cheaper. While it will take a long time (~3 years) for 14/16nm FinFET processes to reach price parity with what 28nm is now, it is dropping in price faster than when the 28nm generation came out due to the massive volumes of Apple, NVIDIA, etc.
It is looking like the 28nm generation will be a mainstay node, with continued investments by the major pure play fabs to keep bringing costs lower.
The other thing we are looking forward to directly test/compare are unums, specifically the new "type 3" ones known as Posits, which are useful (for some definitions of useful) all the way down to 4 bits, and have a greater dynamic range plus greater precision than IEEE floats while using let's bits and theoretically lower area/power on a chip.
Other than we are faster (20% higher clock plus 2x higher IPC) and more efficient (Epiphany is single precision only, where we are twice as efficient as them, we also support FP64), there are three quick points:
1. We actually have double the local scratchpad of Epiphany per core, and our SPM banking and register port scheme actually enables us to operate all four functional units within a core simultaneously, while also having data go in and out of the core on the Network on Chip. With Epiphany, you are very limited in what instructions can run together primarily due to port conflicts... the biggest difficulty is that you can't do any sort of control instructions with anything else.
2. As far as the Network on Chip goes, we are able to guarantee all latencies through a strict deterministic static priority routing scheme. Epiphany had 3 levels of it's Network on Chip, one for stores, one for read requests (8x slower than stores), and one for off chip communications. We have a (patent pending) way of simplifying all of this greatly while reducing latency and having greater bit efficiency.
3. Off chip memory bandwidth is extremely important to us. Even on our test chip, we have 4x higher bandwidth than the Epiphany IV, plus lower latency... our chip to chip and memory interface also uses the exact same protocol as our NoC, simplifying things even further.
There are a handful of smaller things, though my biggest gripe with Epiphany has always been the lack of bandwidth both on and especially off chip. If you are targeting DSP and similar applications like both Epiphany and we are, you really really need to have the ability to saturate your networks and match compute capabilities with it.
We're in the process of getting cross platform benchmarks (HPL, HPCG, FFTW, Coremark, etc) up and running, but I'm hoping we'll be posting results shortly.
2. Since Linux 4.2, there has been a mainline port for STM32 which does not have a MMU, so porting linux is technically possible, though not on our priority list. Something like uCLinux would probably be easier, but not as useful. I have no doubt our cores would be able to handle it, it is just that our current customers already expect their software to be running on bare metal.
We have silicon back, and are now working with early customers in showing a 10 to 25x energy efficiency improvement for high performance workloads.
I gave a talk at Stanford last week that covers the hardware architecture and shows off our development hardware: https://www.youtube.com/watch?v=ki6jVXZM2XU
Check out the talk: https://www.youtube.com/watch?v=aP0Y1uAA-2Y
We will be relaunching the site early next month with developer documentation, demos of our test chip, and a look at the future 256 core production chip.
First 50 minutes or so is an overview on John Gustafson's unum's, followed by the introduction of "type 3 unums" that have two subtypes: Posits (discussed here), and Valids. In short, Posits have a greater mathematical accuracy AND dynamic range of floats, while in many cases also using fewer bits in the representation.
At around the 53 minute mark, the presentation switches over to Dr. Isaac Yonemoto (HN username: dnautics) who gives a live demonstration of a Julia implementation of Posits, showing it preforming favorably for both a FFT and neural network compared to low precision floats.