



|
Via: TOMI | News Archive
| Tags:
CPU,
Sandy Bridge,
Haswell,
TOMI,
Venray,
power wall,
ILP wall,
memory wall
|
|
SO much potential in the opening lines, that slowly flowed down the drain as the article progressed... Good in theory but micro processing technology is best left in the hands of the people who've been doing what they do successfully and satisfying Moore's Law (that the number of transistors that can be placed inexpensively on an integrated circuit doubles approximately every two years, a.k.a. processing power doubles every two years), AMD and Intel |
|
Good idea but it's sort of super optimistic, which kind of dilutes what he was writing about. I have to disagree about the whole thing mainly because if it goes through then it'll limit the upgradability of RAM; I mean if they implemented that method then basically there'd be no way to upgrade the RAM without there being a "wall" and even with the new method, it's still possible that there'd be a wall due to the lack of ways they can connect the installed RAM to the CPU. It's a good idea but I think that it needs a bit more work. |
|
I don't want it if it can't run Crysis on "full". |
|
"TOMI Technology will be built on flash memories creating the elemental unit of a learning machine... the machines will be able to self organize, build robust communicating structures, and collaborate to perform tasks."--> thus skynet will be born lol. |
|
well i have to say it---this is crazyyyyyyyyyyyyyy and impressive,never passed tru my mind DRAM + processor same die O_o....Also, RAM limited what if you want more ram? you have to buy another processor ? not cooo + guys remember this is new, which means of course it will have its limits and we never know what can this bring in the future? remember before it was one core O_o now? you answer it. |
|
I don't think DIMM size is the real problem here. In high-end systems, you'd solve that by having normal DIMMs and TOMI slots. I suppose it'd be possible to build a slot that could take either/or, but you'd probably just separate them. Also, keep in mind that server DIMMs are up to 16GB these days. Certainly large enough to allow for a test system that utilized this sort of concept without running into a RAM wall. |
|
This is a nice concept. The problem is that people try to make a link with actual running systems. We still struggle writing decent software for multicore cpus with single core designed programming languages and libs. This is why we still have under 10 cores per processor on the market. I belive a LEGO approach will do just fine with TOMI concept. All designed from scratch. We have the tools to build other tools. For new hardware, new programming language, new goals. Why cant TOMI be designed to work in a team just like server clouds today but on the same mainboard? |
|
The idea may not be too great upon close examination, but I like that people are considering other methods. x86 is becoming limited so perhaps it's time to consider alternate tech. |
|
for those who doesn't know how TOMI (Thread Optimized Multiprocessor) works here is a video from their site pretty detailed and easy to understand https://www.venraytechnology.com/index.htm |
|
what can this bring in the future? remember before it was one core O_o now? you answer it. |
|
The article jumps too quickly to the Google "brawny cores beat wimpy cores" paper. These are wimpy cores in one dimension: roughly instructions per cycle. They are brawny cores in another dimension: memory bus bandwidth. Google regularly writes single core algorithms that saturate the memory bus. Stick 24 of those processes on a hyperthreaded multi-core Intel processor, and you might as well be using 24 wimpy cores while twiddling your thumbs waiting for memory. The TOMI processor does not reduce power consumption in the traditional way by scaling back the clock frequency; it reduces power consumption by eliminating the overheads of transferring data between a memory chip and a cpu chip. We do not struggle to write software for multi-core chips. Running multiple daemon processes is dead easy. Chrome forks off separate processes for each tab. We don't need your text editor to run faster. We might need your movie editor to run faster. We might want to run more daemons on your desktop, or, more likely, phone so that your computer can keep you better connected to more information. And we might want to run much more advanced applications on your computer than you've previously used before. Yes, moving back to a 32-bit world and a sub-4GByte address space would be a pain. But, geeze, we buy the memory and get the cpu for free. Surely we can find a way to take advantage of all that cpu. |