Stories
Slash Boxes
Comments

SoylentNews is people

posted by chromas on Thursday July 26 2018, @03:41PM   Printer-friendly
from the cloudscale-deeplearn dept.

Google unwraps its gateway drug: Edge TPU chips for IoT AI code; Custom ASICs make decisions on sensors as developers get hooked on ad giant's cloud

Google has designed a low-power version of its homegrown AI math accelerator, dubbed it the Edge TPU, and promised to ship it to developers by October. Announced at Google Next 2018 today, the ASIC is a cutdown edition of its Tensor Processing Unit (TPU) family of in-house-designed coprocessors. TPUs are used internally at Google to power its machine-learning-based services, or are rentable via its public cloud. These chips are specific[ally] designed for and used to train neural networks and perform inference.

Now the web giant has developed a cut-down inference-only version suitable for running in Internet-of-Things gateways. The idea is you have a bunch of sensors and devices in your home, factory, office, hospital, etc, connected to one of these gateways, which then connects to Google's backend services in the cloud for additional processing.

Inside the gateway is the Edge TPU, plus potentially a graphics processor, and a general-purpose application processor running Linux or Android and Google's Cloud IoT Edge software stack. This stack contains lightweight Tensorflow-based libraries and models that access the Edge TPU to perform AI tasks at high speed in hardware. This work can also be performed on the application CPU and GPU cores, if necessary. You can use your own custom models if you wish.

The stack ensures connections between the gateway and the backend are secure. If you wanted, you could train a neural network model using Google's Cloud TPUs and have the Edge TPUs perform inference locally.

Google announcement. Also at TechCrunch, CNBC, and CNET.

Related: Google's New TPUs are Now Much Faster -- will be Made Available to Researchers
Google Renting Access to Tensor Processing Units (TPUs)
Nvidia V100 GPUs and Google TPUv2 Chips Benchmarked; V100 GPUs Now on Google Cloud


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by takyon on Thursday July 26 2018, @04:37PM (2 children)

    by takyon (881) <reversethis-{gro ... s} {ta} {noykat}> on Thursday July 26 2018, @04:37PM (#713207) Journal

    That's the gist of the story. Google and others returning to the edge (as it should be), but trying to maintain some control/lock-in.

    If I want to run a bootleg JARVIS or render DeepFake porn, I want to use my own hardware.

    --
    [SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
    Starting Score:    1  point
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 4, Insightful) by fyngyrz on Thursday July 26 2018, @05:05PM (1 child)

    by fyngyrz (6567) on Thursday July 26 2018, @05:05PM (#713229) Journal

    ...gateway drug...

    Yeah, this. I wouldn't touch this with someone else's ten foot pole. It's just another variation on third-party clouds, and just like 3rd party clouds, it's 100% a very, very bad idea.

    • Google will have your data — and they will abuse it
    • Any part of the intervening net goes down, so does your functionality
    • Google in particular is well known for closing services arbitrarily, leaving users in the lurch

    No thanks. Local solutions much preferred.

    • (Score: 2) by corey on Thursday July 26 2018, @11:45PM

      by corey (2202) on Thursday July 26 2018, @11:45PM (#713454)

      The idea is you have a bunch of sensors and devices in your home, factory, office, hospital, etc, connected to one of these gateways, which then connects to Google's backend services in the cloud for additional surveillance processing.