This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
Product Feedback Forum
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Community
- Product Feedback
- Ability to separately change the caching period fo...
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
At the moment, the caching period of live models is set for the whole instance which removed flexibility where you'd want the caching period to be different for exceptionally large models. For example, we have a table we have to ingest via a live connection as it is too big for elasticubes - but wouldn't want the caching period for this live connection to be too "low" as it would cost a lot via AWS. However, we would want a low caching period for low latency reporting
See more ideas labeled with:
