FB TraceManager 3 - Documentation

What's New in V3.6?

What's New in V3.6?

Previous topic Next topic  

What's New in V3.6?

Previous topic Next topic  

This section discusses the incremental changes in V3.6 compared to V3.5.


High-Level Overview


The following changes/enhancements have been made/added in V3.6:


Hotspots Analysis improvements
Improved Firebird 3 support and compatibility notice
Bugfixes, improved stability, misc


They are discussed in more detail in the following sections.


Hotspots Analysis Improvements


Hotspots Analysis is a very popular area in the product. It gives you a very light-weight and aggregated in-memory view on all traced statements, procedures/functions and triggers. A great starting point to spot the most expensive contributors. In this release, we have added an optional and configurable way to automatically refresh the displayed data. See below the red highlighted area.




Defaults for the trace session can be set in the Register Project wizard.


Additionally, we have made Hotspots Analysis more robust for 24x7 usage, primarily string list representations of data in columns not growing infinitely. Distinct textual values, e.g. transaction IDs etc. are now limited to the 500 most recent entries resulting in not allocating more and more memory when running over a very long time period.


Improved Firebird 3 Support


A few minor changes across the entire product have been made for better support of Firebird 3.


IMPORTANT: Due to a bug (http://tracker.firebirdsql.org/browse/CORE-5203) in Firebird 3 RC1 and later, including the final release of Firebird from April 19, 2016, running a trace session with FB TraceManager may result in:


A single CPU/core is and stays fully utilized on the server until Firebird gets restarted (or the Firebird Classic process gets killed)
FB TraceManager locks up and needs to be killed via Task Manager


So, please DO NOT use the trace facility in FB TraceManager against Firebird 3.0.0 RC1+. The header page, database statistics and monitoring tables areas are NOT affected.


The good news is, that the issue got fixed on the Firebird-side starting with snapshot build: (April 22, 2016). Firebird snapshot builds are available here: http://www.firebirdsql.org/en/snapshot-builds/


Build is pretty much the code base of the final release + the fix for our trace issue, thus we consider that snapshot build as production ready, in case you are in need to use FB TraceManager against Firebird 3 already now in production.


We also have archived the mentioned snapshot builds locally here in our company, in case you do not want to update to the latest snapshot build available. If you have any doubts or questions, feel free to get in touch with us.


Bugfixes, improved stability, misc


FB TraceManager ships with Firebird embedded. We have updated to version 2.5.5. Additionally, a few minor bugs have been fixed.



See also

About FB TraceManager 3

Product Editions

Quick Start Guide

Trace Data Management

FBTMLoggerSvc - About

Database Monitoring