Reduce Cube File Size By Up to 50% Using Cache Compression
This former preview feature, introduced in MicroStrategy ONE Update 10, is out of the box starting in MicroStrategy ONE Update 11.
Starting in MicroStrategy ONE Update 10, you can utilize cache compression to reduce cube file size by up to 50%. As you increasingly generate cubes with data, the resources required to store cube files on disk increases. The time and resources required to keep cubes synced between nodes after edits are made on another node also increase. You can use this feature to slow your resource utilization as it implements fast compression for cube serialization and deserialization. In Microstrategy ONE update 10, this feature is disabled by default. In MicroStrategy ONE Update 11 and newer, this feature is enabled by default. You can enable cache compression using one of the procedures below.
Click here to enable the cache compression preview feature in MicroStrategy ONE Update 10.
-
Open the MicroStrategy REST API Explorer by appending /MicroStrategyLibrary
with /api-docs/index.html?visibility=all
in your browser.
-
Create a session and authenticate it. In the Authentication section, use POST /api/auth/admin/login
.
-
Click Try Out and modify the request body by providing your user name and password.
-
Click Execute.
-
In the response, find X-MSTR-AuthToken
.
-
To get the current feature status:
-
Under the Configurations section, look up GET /api/v2/configurations/featureFlags
.
-
Click Try Out.
-
Set the proper X-MSTR-AuthToken
from step 5. You can also get this via inspecting the browser network XHR requests.
-
Click Execute.
-
Search for FCC
in the response body to find its status details.
-
Under the Configurations section, look up PUT /api/configurations/featureFlags/{id}
.
-
Click Try Out.
-
Set the proper X-MSTR-AuthToken
from step 5. You also can get this via inspecting the browser network XHR requests.
-
Set id
to D148530D519D4CBD5E68307E97FE4674
.
-
To enable this preview feature, set the status
value to 1
.
-
Click Execute.
-
Repeat step 6 to verify that the feature is enabled.