Computer Architecture with Dave Patterson Holiday Repeat
Play • 51 min

Originally published November 7, 2018

An instruction set defines a low level programming language for moving information throughout a computer. In the early 1970’s, the prevalent instruction set language used a large vocabulary of different instructions. One justification for a large instruction set was that it would give a programmer more freedom to express the logic of their programs.

Many of these instructions were rarely used. Think of your favorite programming language (or your favorite human language). What percentage of words in the vocabulary do you need to communicate effectively? We sometimes call these language features “syntactic sugar”. They add expressivity to a language, but may not improve functionality or efficiency.

These extra language features can have a cost.

Dave Patterson and John Hennessy created the RISC architecture: Reduced Instruction Set Compiler architecture. RISC proposed reducing the size of the instruction set so that the important instructions could be optimized for. Programs would become more efficient, easier to analyze, and easier to debug.

Dave Patterson’s first paper on RISC was rejected. He continued to research the architecture and advocate for it. Eventually RISC became widely accepted, and Dave won a Turing Award together with John Hennessy.

Dave joins the show to talk about his work on RISC and his continued work in computer science research to the present. He is involved in the Berkeley RISELab and works at Google on the Tensor Processing Unit.

Machine learning is an ocean of new scientific breakthroughs and applications that will change our lives. It was inspiring to hear Dave talk about the changing nature of computing, from cloud computing to security to hardware design.

The post Computer Architecture with Dave Patterson Holiday Repeat appeared first on Software Engineering Daily.

The Cloudcast
The Cloudcast
Cloudcast Media
An Event-Driven Apps Look Ahead for 2021
James Urquhart (@jamesurquhart, Global Field CTO @VMware, O’Reilly Author) talks about event-driven application architectures, how it's changing real-time business models, and technology stack driven the evolution.  *SHOW: *483 *SHOW SPONSOR LINKS:* * BMC Wants to Know if your business is on its A-Game * BMC Autonomous Digital Enterprise * Datadog Security Monitoring Homepage - Modern Monitoring and Analytics * Try Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirt. * Okta - You should not be building your own Auth * Learn how Okta helped Cengage improve student success rates during COVID. *CLOUD NEWS OF THE WEEK *- http://bit.ly/cloudcast-cnotw *CHECK OUT OUR NEW PODCAST - **"CLOUDCAST BASICS"* *SHOW NOTES:* * Flow Architectures - The Future of Event Streaming & Event-Driven Integration * The Cloudcast Eps.43 - James Urquhart * The Cloudcast Eps.344 - Bringing AI to the Edge (Swim.ai) * The Cloudcast Eps.334 - The Future of Edge Computing (Derek Collison, Synadia) *Topic 1 *- Welcome back to the show. We’ve known you for quite a while, going back to working together on very early Cloud stuff. You’ve always enjoyed being focused on complex, distributed systems. Tell us what you’re focused on these days.  *Topic 2 *- Let’s talk about this concept of “event-driven” and flow. Where did it come from, what does it do, why is it valuable to application designers? *  * *Topic 2a *- What is a “flow” and how is it related to event-driven? *Topic 3 *- Events are data. We’ve had relational databases for data, and then we had NoSQL or eventually-consistent databases for data. Are events a new type of data, or a new way to deal with data in a different context?  (channels, replays, etc.) *Topic 4 *- Can we talk through an example of an event-driven application, or an event-driven integration between multiple organizations? How is it new/different? What unique capabilities does it bring now?  (Kafka, IoT, API Gateways, etc.) *Topic 5 *- Cloud made IT self-service. Serverless made Ops become on-demand. If I’m a business leader, what does event-driven give us?*  * *Topic 6 *- Where are we in the maturity of event-driven architectures? What might be some of the next stages coming in 2021 or 2022?   *FEEDBACK?* * Email: show at thecloudcast dot net * Twitter: @thecloudcastnet
43 min
Kubernetes Podcast from Google
Kubernetes Podcast from Google
Adam Glick and Craig Box
Cilium, with Thomas Graf
Thomas Graf is the inventor of Cilium and the co-founder of Isovalent. Cilium is a container networking plugin built on top of eBPF, bringing modern SDN technologies to accelerate your pods. Adam and Craig also discuss the many uses of Christmas trees. Do you have something cool to share? Some questions? Let us know: * web: kubernetespodcast.com * mail: kubernetespodcast@google.com * twitter: @kubernetespod Chatter of the week * Christmas trees: * Keep clear (mostly) * Culinary uses * Discussed in episodes 104 and 111 News of the week * Google grants $3m to the CNCF to run the Kubernetes infrastructure * AWS Managed Grafana and Prometheus * In partnership with Grafana Labs * Red Hat acquires Stackrox * Windows Containers GA in OpenShift 4.6 * CNCF Annual Report * KubeCon NA 2020 Transparency Report * Rancher announces Harvester * I’ll give you the key * Kubernetes 1.20 feature deep-dives: * Pod impersonation an short-lived volumes * Third-party device metrics GA * More granular control of storage permission * Sonobuoy goes beyond conformance * Project Contour security audit * Pulse: stats from Envoy Mobile * Crossplane 1.0 * Project Karavi from Dell Technologies * Cluster API provider for Microsoft Azure * Vitess project journey report * Tanzu Gemfire * Kubernetes Security Essentials from the CNCF Links from the interview * Chains and tables * Berkeley Packet Filter * eBPF * Episode 91: eBPF and Falco, with Leonard Di Donato * High level languages for kernel developers * eBPF Summit 2020 * Cilium * Is it DNS? * Is it a series of tubes? * BGP * Hubble * Accelerating Envoy and Istio with Cilium * Episode 128: Antrea, with Antonin Bas * Bringing Cilium to GKE with Dataplane v2 * Maglev load balancing connection scheduling * Isovalent * Notes on A16Z’s investment * Thomas Graf on Twitter
41 min
Google Cloud Platform Podcast
Google Cloud Platform Podcast
Google Cloud Platform
2020 Year End Wrap Up
This week, four of the podcast’s greatest hosts come together to celebrate all of the fun and informative episodes we’ve been privileged to do this year! Join Mark Mirchandani, Jon Foust, Priyanka Vergadia, and Brian Dorsey as we talk about our favorite guests and shows, some cool things that happened this year, and what we’re looking forward to in 2021! Cool things of the week * A Giant List of Google Cloud Resources blog * Google Cloud 4 Words site Our favorite episodes * Jon’s Favorites * GCP Podcast Episode 212: Data Management with Amy Krishnamohan podcast * GCP Podcast Episode 237: NVIDIA with Bryan Catanzaro podcast * Priyanka’s Favorite * GCP Podcast Episode 240: reCAPTCHA Enterprise with Kelly Anderson + Spring ML Potholes with Eric Clark podcast * Mark’s Favorites * GCP Podcast Episode 242: NASA and FDL with James Parr and Madhulika Guhathakurta podcast * GCP Podcast Episode 217: Cost Optimization with Justin Lerma and Pathik Sharma podcast * GCP Podcast Episode 228: Fastly with Tyler McMullen podcast * Brian’s Favorites * GCP Podcast Episode 223: Voice Coding with Emily Shea and Ryan Hileman podcast * GCP Podcast Episode 233: Bare Metal Solution with James Harding and Gurmeet Goindi podcast * GCP Podcast Episode 212: Data Management with Amy Krishnamohan podcast Sound Effects Attribution * “Bad Beep” by RicherLandTV of Freesound.org * “Small Group Laugh 6” by Tim.Kahn of Freesound.org * “It’s Always Night in Space” by JamesSilvera of HDInteractive.com * “Easy Cheesy” by LoboLoco of FreeMusicArchive.org
36 min
AWS TechChat
AWS TechChat
Shane Baldacchino
Episode 79 - re:Invent 2020 - App Dev, Containers & Database Wrap
In this episode of AWS TechChat we continue with part two of our four part re:Invent 2020 series with this episode covering all Application Development, Containers, and Database announcements. For our developer community, we talked about: * Using CodeGuru’s new Security detectors to help you find and remediate security issues in your code * Python support for CodeGuru’s in preview * We shared another new service, DevOps Guru in preview, for measuring and improving an application’s operational performance * Lambda now supports up to 10 GB of memory and 6 vCPU cores and a billing granularity reduction down to 1ms * Amazon API Gateway now supports integration with Step Functions StartSyncExecution for HTTP APIs * Appflow simplifies cloud app integrations for connect customers with Customer Profiles * Similarly, Appflow can provide similar app integrations with those 3rd party apps to HoneyCode. * For those Amplify users, deploy Fargate containers through the Amplify CLI and you get a new AdminUI to boot that deploys all the underlying bits for you. * AWS Proton to bridge the gap between platform and development teams In containers we kicked it off with EKS. * First, cluster add-ons managed through the EKS console, CLI, or API. * Run EKS on premises with EKS Distribution * EKS on Fargate now has built in logging with Fluent Bit under the hood * You can now see all your Kubernetes resources in the EKS console without needing extra tools * Public registries for your container images with ECR public and the ECR public gallery * Use your existing containers as a lambda package format * ECS Deployment Circuit Breaker is in preview to stop deployments from getting worse and auto-rollback In database land we covered * Bablefish, not the mythological creature, but a translation layer between Aurora PostgresSQL and Microsoft SQL. * v2 of Aurora Serverless has arrived, considerably faster and scales in a fraction of second, with scaling so fast it is perfect for those event driven applications. * Data Exchange adds revision access rules for governing access * RDS Service Delivery Partners for when you want someone to build, deploy, and manage your RDS deployments * RDS Cross-Region backups comes to RDS for Oracle * Share data across Redshift clusters with data sharing in preview and pull data from partners directly via the RedShift Console. * RedShift Federated query comes to RDS for MySQL and Aurora MySQL * Redshift Automatic Table Optimization to keep your data warehouse running in tip top shape automatically. * Move RedShift clusters easily across Availability Zones. * JSON supports in preview for RedShift * Finally, AQUA comes to RedShift in Preview as a caching layer to speed up queries. Stay tuned as we cover all aspects of re:invent 2020 in our coming multi-part re:Invent update
52 min
The Backend Engineering Show with Hussein Nasser
The Backend Engineering Show with Hussein Nasser
Hussein Nasser
The 2021 Slack Outage (Detailed analysis)
On Jan 4th 2021, Slack experienced a global outage that prevented customers from using the service for nearly 5 hours. Slack has released the Root cause analysis incident report which I’m going to summarize in the first part of this video. After that Ill provide a lengthy deep dive of the incident so make sure to stick around for that. If you are new here, I make backend engineering videos and also cover software news, so make sure to Like comment and subscribe if you would like to see more plus it really helps the channel, lets jump into it. So This is an approximation of Slack’s architecture based on what was the described in the reports. Clients connects to load balancers, load balancers distribute requests to backend servers and backend servers finally make requests to database servers which is powered by mysql through vitess sharding. All of those are connected by routers in cross boundary network. Around 6AM jan 4 , the cross network boundary routers setting between LB and backend and backend to DB started to drop packets. This lead to the load balancers slowly marking backends as unhealthy and removing them from the fleet Which compounded the amount of requests The number of failed requests eventually triggered the provisioning service to start spinning an absurdly large number of backend servers However the provisioning service couldn’t keep up with the huge demand and shortly started to time out for the same networking reasons and eventually ran out of maximum open file handles. Eventually Slack’s cloud provider increased the networking capacity and backend servers went back to normal around 11 AM PST This was a summary of the slack outage, Now set back, grab your favorite beverage and lets go through the detailed incident report! 0:00 Outage Summary 2:00 Detailed Analysis Starts 5:20 The Root Cause 30:00 Corrective Actions --- Send in a voice message: https://anchor.fm/hnasr/message
44 min
Search
Clear search
Close search
Google apps
Main menu