Multithreading has many advantages over single-threaded systems, but it can increase software complexity and make it more difficult to verify.
Traditional verification methods like code review, static analysis and functional testing are necessary but not sufficient
to fully verify multi-threaded embedded software.
Multithreaded architecture offers many advantages for developers, but it may also make the software more complicated and make system verification difficult.
Tracealyzer® version 4.7 in now available for download and evaluation. This is a big feature update with several new capabilities and major improvements. Observability for any C/C++ software: Percepio’s TraceRecorder library can now be used with any C/C++ software...
Learn how to run Tracealyzer 4 on Linux, with requirements and notes on common Linux distributions.
In this blog post, we will see how Tracealyzer can be used to quickly and efficiently evaluate multiple implementations of an algorithm in Python, a language that is becoming more common in embedded application development as most machine learning frameworks are implemented in Python.
In this post, we’re going to understand how the combination of LTTng and Tracealyzer can shine light on how compiler options impact performance. The method discussed can come in handy whenever we are evaluating the performance of multiple candidate implementations of a particular feature.
In this blog post, we’re going to demonstrate how to create LTTng tracepoints and how to use Tracealyzer for Linux to measure certain metrics based on these tracepoints.
When developing an application that’s targeting a Linux-based system, it is important to configure our system to maximize performance, because misconfiguration can limit application performance.
Percepio announces the immediate availability of Tracealyzer version 4.4 with support for embedded Linux. The new version adds several views optimized for Linux tracing to Tracealyzer and leverages CTF, the Common Trace Format, and the widely supported LTTng open source tracing framework.
Today’s post dives into a key component of a Linux device driver, the interrupt handler, and shows how Tracealyzer can give you feedback on the performance of your handler.
While there are mechanisms native to the Linux kernel to ensure that the functionality of a custom-written driver is correct, evaluating performance is not straightforward. Here’s how you can use Tracealyzer for Linux to assess the performance and identify any deficiencies.