September 2024
Intermediate to advanced
260 pages
6h 59m
Spanish
Content preview from Ingeniería de Software para Científicos de Datos
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Capítulo 2. Analizar el rendimiento del código
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
En el Capítulo 1, expuse algunos de los aspectos de escribir buen código, y en este capítulo voy a profundizar en un aspecto: el rendimiento. Si escribes código que forma parte de un sistema mayor, es muy importante que tu código tenga un buen rendimiento. Debe devolver sus resultados a tiempo, y no debe exceder los recursos informáticos disponibles.
Pero antes, lo más importante es que tu código funcione. Antes de aplicar cualquiera de las técnicas de este capítulo o del siguiente, asegúrate de que tu código resuelve el problema que debe resolver y devuelve los resultados que esperas. Cualquier optimización o aumento de velocidad debe producirse después de que el código ya funcione correctamente.
En segundo lugar, pregúntate si es necesario mejorar el rendimiento. Necesitarás conocer las expectativas del sistema más amplio con el que interactúa tu código. ¿Necesita tu código devolver un resultado en un tiempo determinado? ¿Está esperando tu usuario a realizar alguna acción basada en los resultados de tu código? Si es así, cuanto más rápido funcione, mejor será la experiencia del usuario.
Por ejemplo, tu modelo de aprendizaje automático puede necesitar devolver su predicción en 100 ms para poder mostrarla al usuario. Si tu código ya devuelve su resultado dentro del tiempo permitido, puede que no sea necesario dedicar ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.