It looks like Xdebug 3.1 will try to compress trace and profile files by default, depending on availability of zlib.
It would be great if query monitor displayed the current compression settings since not all tools will be able to read these compressed files. For example:
xdebug docs say to disable compression for QCacheGrind
You should be able to determine whether xdebug was compiled with compression support with something like: in_array( 'compression', xdebug_info( 'extension-flags' ), true ).
The xdebug.use_compression setting can then be checked to determine if compression is currently enabled.
These details could probably even be hidden by default and only shown if the current mode includes 'trace' or 'profile'.
Along the lines of #576...
It looks like Xdebug 3.1 will try to compress trace and profile files by default, depending on availability of zlib.
It would be great if query monitor displayed the current compression settings since not all tools will be able to read these compressed files. For example:
You should be able to determine whether xdebug was compiled with compression support with something like:
in_array( 'compression', xdebug_info( 'extension-flags' ), true )
.The
xdebug.use_compression
setting can then be checked to determine if compression is currently enabled.These details could probably even be hidden by default and only shown if the current mode includes
'trace'
or'profile'
.More info: