is there room for optimizing the HTTP traffic in terms of volume by enabling compressioin such as GZIP? I’m not quite familiar with configuration of Apache etc, so before diving into that topic, I would like to understand if such configurations are already out-of-the-box with a default Canvas installation or not.
In theory, there should be two main traffic lanes that may benefit:
- Traffic between TM1 REST API and Cubewise Application Server
- Traffic between Cubewise Application Server and local Web Browser
We have a lot of users on the other side of the world, and they benefit from each byte that has not to be sent around directly (referring to point 2). Coming from TM1Web, Canvas is already a huge step forward also in terms of responsiveness. But is HTTP compression enabled by default or is it worth to dive into configuration to further optimize the user experience?
What’s your experience and recommendation?
Thanks a lot,