Mediaspace scheduled maintenance: Aug 25, 2026 07:00 - 12:00 AM. During this time, videos will be temporarily unavailable. Check status updates.

Lecture

Software Performance

In course

CS-305: Software engineering

This course teaches the basics of modern software development: designing software, working in a team, writing good code, shipping software, and evolving software. It emphasizes building software that meets high standards of quality, reliability, security, ...

Description

This lecture by the instructor covers the definition and quantification of software performance, including how to set performance goals, measure performance metrics, and improve software performance. It discusses latency percentiles, dealing with performance in practice, and various commands related to performance. The lecture also delves into concepts like caching, batching, laziness, speculation, and debugging performance problems. Examples from real-world scenarios, such as Grand Theft Auto, are used to illustrate performance optimization techniques and back-of-the-envelope calculations for latency. Continuous Performance Testing (DevOps) is also explored, emphasizing the importance of performance testing in the development process.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Instructor

George Candea

Official source

Related concepts (32)

Software metric

In software engineering and development, a software metric is a standard of measure of a degree to which a software system or process possesses some property. Even if a metric is not a measurement (metrics are functions, while measurements are the numbers obtained by the application of metrics), often the two terms are used as synonyms. Since quantitative measurements are essential in all sciences, there is a continuous effort by computer science practitioners and theoreticians to bring similar approaches to software development.

Continuous integration

In software engineering, continuous integration (CI) is the practice of merging all developers' working copies to a shared mainline several times a day. Nowadays it is typically implemented in such a way that it triggers an automated build with testing. Grady Booch first proposed the term CI in his 1991 method, although he did not advocate integrating several times a day. Extreme programming (XP) adopted the concept of CI and did advocate integrating more than once per day – perhaps as many as tens of times per day.

Continuous delivery

Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, following a pipeline through a "production-like environment", without doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production.

Real-time computing

Real-time computing (RTC) is the computer science term for hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines". Real-time responses are often understood to be in the order of milliseconds, and sometimes microseconds. A system not specified as operating in real time cannot usually guarantee a response within any timeframe, although typical or expected response times may be given.

Software testing

Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not necessarily limited to: analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc.

Related lectures (34)

Software Testing: Avoiding and Fixing Bugs

Emphasizes the critical role of software testing in preventing and resolving bugs during development.

Programming Bugs: Understanding, Fixing, and Preventing

Explores programming challenges, debugging techniques, software testing, and security practices in software development.

Understanding Microcontrollers: Debugging

Covers the debugging process for microcontrollers, emphasizing code structuring and signal state verification using tools like logic probes and oscilloscopes.

Digital Project Creation: Conclusion

Covers the process of creating a digital project and concludes with tips for guiding children in project creation.

Microcontrollers Simulation: AVRstudio4