The ability to compress SBDF files should improve performance when working with SBDF files. One could more easily store the SBDF files in the Spotfire Library. One should get better performance when using the compressed SBDF files since the compressed files would transmit quicker over the network. The option to compress SBDF files will need to be added to the Automation Services task for exporting SBDF files.
Implemented in | 12.0 |
Hi,
I'm happy to announce that library version history has been implemented in Spotfire 12.0 LTS.
Library items imported into, or exported from, the Spotfire library are now compressed using the gzip format.
This change provides more efficient use of library space, whether the library is stored in the Spotfire database or using an external storage mechanism. Library compression works with all supported databases.
The Library operations are transparent as without compression.
For more information, see the What's new in Spotfire 12.0 LTS and the release notes and product documentation.
Thanks!!
Hello,
I understand the benefit of the proposed solution.Though, the expectation from several members of the community is to get smaller/compressed SBDF files when generated with the "TIBCO Spotfire® C# or JAVA SBDF Library" . Can we hope the RLE compression be ported in these libraries?
Thanks,
Eric.
@Eric, I can't share information about future directions. But I'll be interessed to here about your use cases. I will reach out to you via email to schedule a short call.
Thank you Arnaud, this is great! Do you have an idea of when this compression feature will be avaialble in the Spotfire Java SBDF Library ?
Yes Eric, it relates to this idea. Spotfire 11.7 include RLE compression for TERR data functions and when exporting to SBDF files. This idea was not marked as implemented since there are other areas in the product where compression of SBDF files may be implemented.
I read this in the Spotfire 11.7 "What's new" post (https://community.tibco.com/wiki/whats-new-tibco-spotfirer-117#toc-12):
Faster TERR data functions and SBDF export
Run-length encoding (RLE) compression is now used for faster TERR data function execution and faster export of SBDF files.
RLE is a form of lossless data compression. You will see the biggest improvements with images or texts were you have long runs of identical pixels or strings.
Is this related to this "idea"?
With more users working remotely via VPN, we really need the capability to have the SBDF data compressed while transferring the data to the Spotfire clients.
This is a great idea and should absolutely be implemented - faster file transfer and reduced storage space seem like easy big wins.
With TIBCO expending the Data Functions capabilities in 10.x+ versions, the ability to work with smaller sbdf files will be great. Compression rates show significant improvement. Ideally this should be available natively in the Spotfire engine and the open source SBDF Java Library
SBDF files are a key capability in promoting reuse of data across reports. They can get very large, and once loaded inside reports (stored data) the report compression kicks in and the reports are often a fraction of the size of the SBDF. But their physical size on disk is often an issue, both when getting created and when being read. Compression would be a massive help.
Another reason to do is is that we hit limits on the size of data files saved within Oracle based on Blob size limitations - so compressing SBDF within the library would allow storage of much larger files.