Uncategorized

Why Hypernet? Computing Yesterday, Today, and Tomorrow.

By April 27, 2018 No Comments

Hypernet is building an application programming interface (API) that takes your code and runs it across a cluster of internet connected devices, anything from servers to refrigerators (the “industrial internet”), saving you time and money. Many of you have been asking how we can make this claim, and what makes Hypernet a new and useful tool. By the end of this post, you will have a technical understanding of how Hypernet is changing the computing landscape, how you can get involved, and how you can benefit.

Yesterday

Yesterday, if you wanted to run a complex program like a deep-learning AI or a weather simulation, you had one of two options: use your local machine or upload it to the cloud. Both these options pose huge problems.

Local Machines: Your local machine may be too weak to perform the task you’re interested in. Even Google, with its huge server banks, took two weeks to train its flagship Inception AI, and every time they want to modify it, they have to train it again. Imagine how long it would take you to do that on your own computer — a year? Maybe longer? Since the average person doesn’t have the money to spend on a server bank or the time to waste running programs locally, this solution doesn’t make sense.

Cloud Computing: Even the cloud has major limitations. The idea of subscription cloud services is that you can “buy time” on a bigger, better computer, basically leasing it for the time it takes to run your program. But these computers are expensive, and their cost gets passed on to you. Also, there is a limited number of these computers available, so not only do you need to fight with others for a modest number of computers, but if you want to requisition 100,000 of them to run a massively parallel program, no company would be able to service that. Trust us — we’ve tried calling a company and asking for time on 100,000 separate computers, and all we got was a very confused and embarrassed team of engineers on the other line.

There’s also the issue of latency; these computers are far away from you, meaning in practice it takes time just to send your data back and forth with a data center, let alone compute the answer.

Clearly, cloud computing has high overhead costs, problems running massively parallel programs, and inherent latency that make it practically useless for many applications, including real-time ones.

​Today

​Yesterday is over: some companies have identified the same problems with local or cloud programming. Simply identifying that there is a problem is not enough. What you need is the ability to run any program you want — parallel, vectorized, anything — on a distributed network efficiently and completely decentralized. No other cloud or distributed computing company can do that. Other distributed computing solutions can only handle trivial algorithms like rendering or can only maximize specially formatted code instead of allowing you to run any problem in parallel like on the Hypernet.

Tomorrow

​If the cloud is yesterday and distributed computing is today, the Hypernet is tomorrow.

Hypernet solves all the problems posed by servers and the cloud. As devices join our network, you don’t have to pay for the cost of those devices. Furthermore, the combined power of those devices is greater than that of a server system. Also, Hypernet distributes the computational workload across a cluster of internet connected devices, starting with the ones nearest to you (subject to your constraints for processor speed, RAM, etc.) This means you don’t pay a hardware premium and you don’t have to worry about having too few computers or too much latency.

If you’re excited about the implications of Hypernet technology and are wondering how it works along with more technical details, stay tuned for our next post. We’ll reveal exactly how our algorithms run and how they are different from anything else available.

​Until then, feel free to contact us on Slack or Reddit.

Best,

– Ivan Ravlich and the Hypernet team

Leave a Reply