Linux Debugging and Performance Tuning: Tips and Techniques (Anglais) Broché – 10 octobre 2005
|Neuf à partir de||Occasion à partir de|
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Les clients ayant acheté cet article ont également acheté
Description du produit
Quatrième de couverture
Learn Linux debugging and optimization—at kernel and application levels—hands-on!
This is the definitive guide to Linux software debugging and performance optimization at both the kernel and application levels. Using extensive Linux code examples, Steve Best systematically introduces open source tools and best-practice techniques for delivering bug-free, well-tuned code.
Drawing on his exceptional experience optimizing Linux systems for IBM, Best covers issues ranging from memory management and I/O to system processes and kernel bug messages. You'll walk through real debugging sessions, discovering the strategies experts use to debug even the most complex application- and kernel-related problems. You'll master sophisticated profiling techniques for identifying and resolving bottlenecks more quickly and learn how to capture the right data in the event of trouble. Coverage includes
Debuggers: gdb, kgdb, and KDB
/proc kernel data analysis
System process monitoring
Oops bug messages
Syslog and event logging
Profiling kernel behavior
Crash dump analysis
Linux® Debugging and Performance Tuning will be indispensable for every developer who needs to supercharge the Linux kernel and applications, and for every administrator and support specialist who must resolve Linux reliability or performance issues.
© Copyright Pearson Education. All rights reserved.
Biographie de l'auteur
Steve Best works in the Linux Technology Center of IBM in Austin, Texas. He is currently working on Linux storage-related products. Steve has led the Journaled File System (JFS) for Linux project. Steve has worked on Linux-related projects since 1999 and has done extensive work in operating system development focusing on file systems, internationalization, and security. Steve is the author of numerous magazine articles, many presentations, and the file system chapters in Performance Tuning Linux Servers (Prentice Hall PTR 2005).
© Copyright Pearson Education. All rights reserved.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
Commentaires client les plus utiles sur Amazon.com
In the next version, it would be nice to have Xenmon, SystemTap, Perfmon2 & section on general hw counters (TLB miss, memory latency). Two pages(277-278) for cache misses is weak.
Typically, many linux programmers don't get beyond using gcc. The book shows the power in the above tools, that can greatly enhance your understanding and performance of the code. Of these, I would consider gprof to be the most useful. You can see where the CPU spends most of its time when running your code. So you can focus on optimising the appropriate routines. Otherwise, it's very easy to get sidetracked streamlining a routine that has no appreciable overall effect on performance.
While the book treats gprof, gdb and gcov equally, I would recommend that you first get facile with gprof, for perhaps the best payoff.
The book also has lengthy treatments of other tools and methods. These tend to be for system administrators and developers of tools for those people. (Whereas the earlier tools are available to any user.) For example, the mysterious /proc is shown to be a nifty viewport into the runtime kernel activity. Without it and its associated tools, the latter could be largely a black box.
Also, to the extent that you can, when accessing /proc, try doing this very carefully. Type slowly and check what you have typed, before pressing return. Yes, this sounds mundane. But it is possibly to really muck up the system.
More specifically, it's a programmer's book that takes debugging all the way to the kernel, investigating tracing problems right down to kernel level. There's in depth coverage of the tools you need to do this and good case study examples are employed.
This is deeper than many will want to go, but if you do want to get into this level of debugging, this is a great place to start.
The stated audience is "people developing or supporting Linux applications/kernels". As a system administrator, this is where my interest (and biases) show.
The book jumps in head first without a true intro to the subject of the first chapter (profiling). This style is consistent throughout the book which prevents this book from being a helpful tutorial, step by step guide, or classroom ready book towards learning debugging/performance tuning (sadly, as this subject could benefit from developers/administrators being firmly educated in these processes). Additionally a lot of space seems wasted on screen shots and sample code that doesn't contribute to the learning process. That said, the book does cover many useful and less well known tools. If you are looking for a reference book to assist in learning more about the arcane (and senior) skills of debugging and performance tuning, this would be a good choice. It doesn't go into great depths, so can be perceived as an introductory guide. It's less of a guide and more of an introduction that will assist a medium experienced administrator to obtaining useful search terms.
I had forgotten that I had reviewed this book previously, and after re-reading the first 3 pages (literally) and deciding that I should check to see what other folks said about this book, I've realized that I was being super-positive in reviewing. As some of the lower rating folks have indicated, this book really wastes a lot of space in pointless diagrams. On page 4 there is a big picture of execution time shown on a watch. This is just an example of how the technical editors did not take time to really edit this book to have useful information and use pictures/diagrams to increase the understanding of the concepts presented. This book is not oriented at all towards administrators, and it seems like an afterthought to include them and have the title "performance tuning".
Anyone experienced will find themselves frustrated by the lack in crisp direction, anyone junior will be confused by the pointless additional pages. This is not a great reference book. This has a few interesting pieces of information, but it's lost in the overall book.
I recommend that a potential reader borrow this book from someone and skim it. Don't buy it
Rechercher des articles similaires par rubrique