Ramirez Samuel C (8 results)

Taschenbuch. Condition: Neu. Neuware.

Taschenbuch. Condition: Neu. Neuware.

Paperback. Condition: new. Paperback. Have you ever profiled a kernel, seen it hit a wall well below the throughput the hardware should be capable of, and had absolutely no idea why?That question is really what this book is for.Most GPU programming resources stop at the point where your code compiles and runs correctly. They teach you how to write parallel kernels, how to manage memory, how to launch a grid of threads - and then they leave you there, assuming the compiler will handle everything else. For a lot of work, that's fine. But if you've ever asked yourself why two kernels that look almost identical on paper perform completely differently in practice, or why a profiler keeps telling you something is "memory-bound" without ever explaining what to actually do about it, you already know that stopping at the high-level language isn't enough.So what does this book actually cover?It takes you underneath the compiler, into the native assembly instructions that a modern parallel processor actually executes - how to read them, how to disassemble compiled code and understand what you're looking at, and how to connect what you see in that low-level output back to the C++ you originally wrote. From there, it works through the full stack of what real performance engineering involves: how thousands of threads actually get scheduled on the hardware, why memory access patterns can make or break your throughput, how synchronization and atomic operations behave under contention, and how to squeeze more out of individual instructions once the bigger structural issues are solved.Is this only for people chasing raw speed for its own sake?Not really. A lot of it is about knowing where your time is actually being spent, rather than guessing. You'll work through how to use profiling tools properly - not just running them and staring at a wall of numbers, but reading the metrics that actually tell you whether you're bound by computation, by memory bandwidth, or by something more subtle like poor occupancy or unnecessary synchronization. There's a full section on debugging at this level too, for the kind of bug that doesn't show up consistently and doesn't make sense until you can see what individual threads are actually doing.Who is this actually written for?Honestly, it assumes you already know how to write and launch parallel kernels. If you're completely new to GPU programming, this probably isn't your starting point - but if you've written kernels before and you're ready to understand what happens after you hit compile, this is built for exactly that stage. It's aimed at engineers working on machine learning infrastructure, people doing high-performance and scientific computing, anyone building latency-sensitive graphics or real-time applications, and honestly, anyone who's just curious enough about what's happening inside the hardware to want the real answer instead of a surface-level one.Does it stay theoretical, or is it actually practical?Every concept in this book is tied to real, disassembled code and real profiler output - not abstract descriptions of what "should" happen. You'll see actual instruction sequences, actual before-and-after comparisons, and actual case studies of kernels being diagnosed and rebuilt from the ground up. It also covers mixed-precision computation, multi-device scaling, and how to build a repeatable, professional workflow around performance work - the kind of process that holds up in a real engineering team, not just in a one-off benchmark.If you're tired of performance tuning that feels like guesswork, this is meant to be the book that finally makes it feel like engineering instead. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Condition: New. Print on Demand.

Paperback. Condition: new. Paperback. Ever opened up a microcontroller project, gotten the classic blinking LED working in an afternoon, and then hit a wall the moment you tried to build something real?Maybe you added a second sensor and suddenly your timing fell apart. Maybe your Wi-Fi connection worked fine on your desk and then dropped constantly once you moved the device to another room. Maybe you tried to add an over-the-air update feature and realized, halfway through, that you didn't actually understand how your board's flash memory was organized. If any of that sounds familiar, this book was written for you.This is not a beginner's tutorial that teaches you to copy code and hope it works. It's a working engineer's guide to building firmware the way it's actually built for real, shipped products - the kind that need to run for months without a restart, survive a lost Wi-Fi connection without falling over, and update themselves safely in the field without ever bricking.So what's actually inside?You'll start with the fundamentals most tutorials skip entirely: how a real-time operating system schedules tasks, why your peripherals need to be configured a certain way to avoid mysterious crashes, and how to structure a project so it doesn't turn into an unmanageable tangle of code six months in. From there, the book walks you through wireless connectivity in real depth - Wi-Fi, Bluetooth Low Energy, mesh networking, and the standards reshaping the smart home industry right now - along with the cloud protocols (MQTT, HTTP, WebSockets) that let your device actually talk to the outside world.Then it gets serious. You'll learn how to debug a device that's already crashed in someone's home, how to properly secure a device so it isn't the weak link an attacker walks through, how to manage battery life so your product survives on a coin cell for a year instead of a week, and how to prepare firmware for an actual manufacturing run rather than just your own desk. There's a full section on running lightweight machine learning models directly on the chip, and a closing set of chapters on documentation, code review, and career paths, because writing firmware that works is only half the job - writing firmware a team can maintain is the other half.Who is this actually for?If you're a software engineer moving into embedded work for the first time, this book gives you the mental models you're missing. If you've been working with simplified hobbyist frameworks and want to understand what's really happening underneath, this walks you through that transition directly. And if you're already a working embedded or IoT engineer, this is built to double as a reference you'll actually come back to.One honest note before you buy: this is a technical book, and it assumes you're comfortable with C and have at least a basic grasp of how digital electronics work. It doesn't hold your hand through "what is a variable." It does, however, walk through a genuinely large number of real, tested code examples, step by step, explaining not just what to type but why a particular approach is the right one.If you're ready to stop patching together tutorials and start building firmware you'd actually be comfortable shipping, this is that book. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

Condition: New. Print on Demand.

Paperback. Condition: new. Paperback. Have you ever profiled a kernel, seen it hit a wall well below the throughput the hardware should be capable of, and had absolutely no idea why?That question is really what this book is for.Most GPU programming resources stop at the point where your code compiles and runs correctly. They teach you how to write parallel kernels, how to manage memory, how to launch a grid of threads - and then they leave you there, assuming the compiler will handle everything else. For a lot of work, that's fine. But if you've ever asked yourself why two kernels that look almost identical on paper perform completely differently in practice, or why a profiler keeps telling you something is "memory-bound" without ever explaining what to actually do about it, you already know that stopping at the high-level language isn't enough.So what does this book actually cover?It takes you underneath the compiler, into the native assembly instructions that a modern parallel processor actually executes - how to read them, how to disassemble compiled code and understand what you're looking at, and how to connect what you see in that low-level output back to the C++ you originally wrote. From there, it works through the full stack of what real performance engineering involves: how thousands of threads actually get scheduled on the hardware, why memory access patterns can make or break your throughput, how synchronization and atomic operations behave under contention, and how to squeeze more out of individual instructions once the bigger structural issues are solved.Is this only for people chasing raw speed for its own sake?Not really. A lot of it is about knowing where your time is actually being spent, rather than guessing. You'll work through how to use profiling tools properly - not just running them and staring at a wall of numbers, but reading the metrics that actually tell you whether you're bound by computation, by memory bandwidth, or by something more subtle like poor occupancy or unnecessary synchronization. There's a full section on debugging at this level too, for the kind of bug that doesn't show up consistently and doesn't make sense until you can see what individual threads are actually doing.Who is this actually written for?Honestly, it assumes you already know how to write and launch parallel kernels. If you're completely new to GPU programming, this probably isn't your starting point - but if you've written kernels before and you're ready to understand what happens after you hit compile, this is built for exactly that stage. It's aimed at engineers working on machine learning infrastructure, people doing high-performance and scientific computing, anyone building latency-sensitive graphics or real-time applications, and honestly, anyone who's just curious enough about what's happening inside the hardware to want the real answer instead of a surface-level one.Does it stay theoretical, or is it actually practical?Every concept in this book is tied to real, disassembled code and real profiler output - not abstract descriptions of what "should" happen. You'll see actual instruction sequences, actual before-and-after comparisons, and actual case studies of kernels being diagnosed and rebuilt from the ground up. It also covers mixed-precision computation, multi-device scaling, and how to build a repeatable, professional workflow around performance work - the kind of process that holds up in a real engineering team, not just in a one-off benchmark.If you're tired of performance tuning that feels like guesswork, this is meant to be the book that finally makes it feel like engineering instead. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Paperback. Condition: new. Paperback. Ever opened up a microcontroller project, gotten the classic blinking LED working in an afternoon, and then hit a wall the moment you tried to build something real?Maybe you added a second sensor and suddenly your timing fell apart. Maybe your Wi-Fi connection worked fine on your desk and then dropped constantly once you moved the device to another room. Maybe you tried to add an over-the-air update feature and realized, halfway through, that you didn't actually understand how your board's flash memory was organized. If any of that sounds familiar, this book was written for you.This is not a beginner's tutorial that teaches you to copy code and hope it works. It's a working engineer's guide to building firmware the way it's actually built for real, shipped products - the kind that need to run for months without a restart, survive a lost Wi-Fi connection without falling over, and update themselves safely in the field without ever bricking.So what's actually inside?You'll start with the fundamentals most tutorials skip entirely: how a real-time operating system schedules tasks, why your peripherals need to be configured a certain way to avoid mysterious crashes, and how to structure a project so it doesn't turn into an unmanageable tangle of code six months in. From there, the book walks you through wireless connectivity in real depth - Wi-Fi, Bluetooth Low Energy, mesh networking, and the standards reshaping the smart home industry right now - along with the cloud protocols (MQTT, HTTP, WebSockets) that let your device actually talk to the outside world.Then it gets serious. You'll learn how to debug a device that's already crashed in someone's home, how to properly secure a device so it isn't the weak link an attacker walks through, how to manage battery life so your product survives on a coin cell for a year instead of a week, and how to prepare firmware for an actual manufacturing run rather than just your own desk. There's a full section on running lightweight machine learning models directly on the chip, and a closing set of chapters on documentation, code review, and career paths, because writing firmware that works is only half the job - writing firmware a team can maintain is the other half.Who is this actually for?If you're a software engineer moving into embedded work for the first time, this book gives you the mental models you're missing. If you've been working with simplified hobbyist frameworks and want to understand what's really happening underneath, this walks you through that transition directly. And if you're already a working embedded or IoT engineer, this is built to double as a reference you'll actually come back to.One honest note before you buy: this is a technical book, and it assumes you're comfortable with C and have at least a basic grasp of how digital electronics work. It doesn't hold your hand through "what is a variable." It does, however, walk through a genuinely large number of real, tested code examples, step by step, explaining not just what to type but why a particular approach is the right one.If you're ready to stop patching together tutorials and start building firmware you'd actually be comfortable shipping, this is that book. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…