This site uses cookies to improve your experience. By viewing our content, you are accepting the use of cookies. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country we will assume you are from the United States. View our privacy policy and terms of use.

Remove Data Engineering Remove Serverless Remove Software Engineering Remove Training
article thumbnail

Sustainability at AWS re:Invent 2022 All the talks and videos I could find…

Adrian Cockcroft

FEBRUARY 13, 2023

Provides comparison of inference workload on P4dn GPU instances vs. AWS Trainium saving 92% energy and 90% cost, and training workload on P4dn vs. AWS Inferentia 2.6x shorter training time, saving 54% energy and 75% cost. Building a data lake of detailed information about energy use of many physical devices.

AWS 64
AWS Energy Architecture Programming 64
article thumbnail

Organise your engineering teams around the work by reteaming

Abhishek Tiwari

JULY 20, 2019

Over specialisation is considered good in industries such as healthcare and aviation but in software engineering over specialisation can be a blocker. Unlike healthcare and aviation where practices don't change over the decades, software technology is changing every day. product) don't change over a long period. Probably yes.

Engineering 61
Engineering Retail Airlines Healthcare 61
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

 

Stay Connected

Join 5,000+ Insiders by signing up for our newsletter

About
About
Editions
Editions
Topics
Powered by Aggregage | Terms and Conditions | Your California Rights and Privacy Policy
© Aggregage 2024