There are two main impediments in automotive software development: high processor cost and poor performance. Performance is particularly important for any safety-critical system that relies on real-time responses, low latency, and high throughput.
Adding more software on a single processor can reduce the hardware needed, keeping tasks on track and lowering costs. High-performance processors do most of the work using efficient software. These stringent performance demands tend to arise when designing for automotive systems in general, and (safety-critical) subsystems in particular. In these instances, processing must be done in real-time, with low latency and high throughput.
However, as often highlighted in discussions about the long tail trend, these performance demands may be difficult to satisfy if architecture remains tightly coupled to particular technologies in the face of changing systemic demands. The Data-Oriented Design (DOD) approach may offer solutions to some of these problems by maximizing performance and lowering costs through optimized data layout and access patterns.
In this blog, we focus on how DOD can help address these two impediments, using the long tail concept described in the book by Richard Fabian.
DOD involves designing a data domain first, then defining how objects interact within that domain, to optimize data layout and access patterns – crucial for enhancing program performance. In contrast, traditional programming paradigms such as Object-Oriented Design (OOD) are based on objects and the interactions between them without the same emphasis on optimizing data flow and access
The core principles of DOD are optimized data layout and efficient data access. Its primary goal is to organize data in a way that maximizes the performance of the hardware – in particular, the CPU and the memory subsystem – ensuring the highest possible throughput to be delivered with the lowest possible latency. DOD aligns data structures with the hardware’s optimal performance characteristics, minimizing, bottlenecks and avoiding inefficiencies that can strain the system.
A traditional Object-Oriented Design OOD design focuses on objects, their relationships, and behaviors and can lead to designs that become abstract and less efficient at handling data. This often results in data being spread throughout various memory locations, causing cache misses and inefficient utilization of the CPU’s cache structure. Data-oriented design addresses this issue by ensuring that related data are stored together thereby reducing cache misses and making better use of the CPU’s memory hierarchy.
Here are the advantages of a data-oriented design system:
While there are advantages, some disadvantages need to be considered including:
There are two types of data structures for memory layout: Structure of Arrays (SoA) and Array of Structures (AoS). In an AoS layout, data is grouped by objects. Each object contains multiple fields, leading to scattered memory access when processing a specific field across all objects. This results in inefficient cache usage, as the CPU cache lines get filled with irrelevant data.
For example:
```cpp
struct SensorData {
float position[3];
float velocity[3];
float distance;
};
std::vector<SensorData> sensorData;
```
In an SoA layout, data is grouped by type, enabling contiguous memory access for each field. This method significantly improves cache utilization, as the data required for computation is more likely to be loaded into the cache, reducing the number of cache misses and aligning with the long tail trend discussed in Richard Fabian’s book cited earlier.
For example:
```cpp
struct SensorData {
std::vector<float[3]> positions;
std::vector<float[3]> velocities;
std::vector<float> distances;
};
SensorData sensorData;
```
By grouping data that is likely to be accessed together, DOD decreases cache misses and boosts memory access efficiency. Optimized access patterns align with the way data is processed, enabling effective prefetching and minimizing the time the CPU spends waiting for data to be loaded from memory.
For example, in computer graphics rendering applications like gaming engines, where noisy high-speed behavior with low precision is often preferred, DOD has been effectively used with massively parallel graphics processors to achieve impressive speedups. Similarly, financial systems that process large datasets in real time have also benefited from DOD, especially in large-scale deployments. These use cases indicate that DOD can be highly advantageous for systems requiring low latency and cost-effective real-time data processing.
Below are several techniques for applying Data-Oriented Design in software development:
Here are some current trends in Data-Oriented Design:
By guiding engineers to optimize code to maximize data placement and access, Data-Oriented Design (DOD) effectively addresses the twin challenges of both performance and cost in a powerful, practical way. DOD reduces reliance on expensive hardware by leveraging resource-sensitive software, leading to more efficient automotive software solutions that are more innovative, affordable, and efficient. Automotive software startups, OEMs, and Tier 1s should embrace DOD principles and tools to maximize their potential.
Unlock the full potential of your automotive software with Data-Oriented Design. Enhance performance, reduce costs, and drive innovation in your projects. Contact us today to discover how DOD can transform your development process!
Other Articles
Model-Based Systems Engineering (MBSE) offers a robust framework to streamline the entire engineering process, from design to validation. Learn more about it here.
Model-Based Systems Engineering (MBSE) offers a robust framework to streamline the entire engineering process, from design to validation. Learn more about it here.
Explore the evolution of functional safety, its growing importance in industries like automotive, and the critical role of Fault Tolerant Time Interval (FTTI) in ensuring system reliability. Learn how FTTI, along with Malfunctioning Behavior Manifestation Time (MBMT) and Hazard Manifestation Time (HMT), contributes to robust safety designs, preventing hazards in safety-related systems such as ADAS and autonomous vehicles. Discover the impact of ISO 26262 standards on the development of effective fault detection and reaction mechanisms in automotive safety.
While ISO 26262 primarily addresses functional safety, SOTIF extends the scope to focus on potential hazards arising from system behaviour, even when the system functions as intended. Learn more about it here.
Discover the risks of reinterpret_cast in safety-critical software and explore safe alternatives like polymorphism and templates for robust, efficient code.
In a rapidly evolving technological landscape, the demand for systems that can not only withstand errors but also adapt to them is paramount. This article delves into the world of Fault-Tolerant (FT) systems, emphasizing their significance in maintaining the functionality and safety of critical operations across various sectors. It explores the latest advancements in FT technology, underscoring the importance of resilience and adaptability in ensuring uninterrupted service and safeguarding against potential failures.
In a rapidly evolving technological landscape, the demand for systems that can not only withstand errors but also adapt to them is paramount. This article delves into the world of Fault-Tolerant (FT) systems, emphasizing their significance in maintaining the functionality and safety of critical operations across various sectors. It explores the latest advancements in FT technology, underscoring the importance of resilience and adaptability in ensuring uninterrupted service and safeguarding against potential failures.
Discover the transformative impact of Software-Defined Networking (SDN) and Multicast Addressing on automotive embedded systems. Explore how these technologies enhance communication efficiency, safety, and performance in the automotive industry, leading to cost-effective, scalable, and eco-friendly solutions. Dive into the technical advantages and practical applications for modern vehicles and infrastructure.
Discover how ChatGPT revolutionizes engineering with AI, accelerating learning, enhancing safety, and boosting productivity.
Defect Escape Reduction Rate and feedback loop elevate testing. Learn more about them here.
ASPICE and ISO26262 frameworks improve system development in the automotive industry, ensuring safety, compliance, and high-quality standards.
Conducting software FMEA, FTA, and compliance with ISO 26262 helps developers create software that meets stringent safety requirements. Learn more about it here.
Explore the challenges of dynamic memory allocation in critical software, learn how to mitigate failures, and ensure the reliability of safety-critical systems. Real-life failures and practical solutions are discussed.
Strong types are a key concept in C++ programming for functional safety. Learn how strong types can reduce errors in critical systems with C++.
Unit testing is an essential part of the software development process. Learn more about it here.
Learn about categorizing requirements, including functional, non-functional, performance, interface etc for effective system management and development.
Writing clear and unambiguous requirements for the automotive industry is important to avoid potential safety risks. Learn more about it here.
Separating requirements and implementation in software engineering enhances the quality and reduces rework.
Learn the complexities of achieving end-to-end protection in automotive systems including meeting freedom from interference and ASIL requirements.
E2E protection is essential for vehicle safety. Learn about the benefits and risks such as undetected cumulative delays from systematic faults and their solutions here.
