Ability to force users to only be able to use "Cache filters on demand" filter cache option

Just to elaborate. We are running a multi-tenant environment and had severe stability problems on the DWH and Yellowfin Server level because one tenent refreshed the filter cache and the server was then refreshing the filters for all tenants. Therfore we would like to turn off/remove the cached filter option alltogether in lieu of the cache filters on demand option.

Since it turned out that using the on demand option drags down the overall system performance even more, you can disregard this idea.

Hi Ingo,

We do have an option that will stop report writers from creating a cached filter when generating the report.

This does however mean they cannot create ANY type of cached filter.

I guess you were trying to force people to use a particular cached filter type, but since that hasn't' given you the results you were after, there is no need to go forward with the enhancement request.

Is that correct?

Thanks,

David

Hi David,

we wanted to force to this option since we thought that would prevent heavy loads on other client_orgs when one client_org refereshes a filter cache. But the effect was worse, since now the filter cashes were refreshed each time a report was open, which was disasterous for the overall performance of the DWH.

So this idea can go in the bin. Thanks

Best reagards,

Ingo

I'm re-opening this idea, as it has now been requested by another user.

Just to be clear, we're after an option to enforce a user to only have the following cached filter options:

- Cached filter on demand

- Custom Query Cached On Demand

This is to stop people caching full result sets when using data source substitution.

Regards,

David

Hi David,

Our goal is to prevent to have cache filter refreshes running over all client-orgs / substituted data sources especially when triggerd by accident from users.

We thought the cached filter on demand would help there, but it turned out to be even worse, since now every report call causes the cache to refresh in that client-org.

Since then we found out, that you can prevent users from refreshing and adding new cached filters.

In short we don’t need that feature anymore, but we would like a feature like the regular cached filters which is not going over all client_orgs / substituted data sources.

Best regards,

Ingo

Von: Yellowfin Support [mailto:support@yellowfin.bi]

Gesendet: Donnerstag, 15. Juni 2017 04:45

An: Ingo Klose

Betreff: New Comment in "Ability to remove cache filter options"

Hi Ingo,

Just circling back on this, as I believe this idea may no longer be needed with the cached filter change that came in 7.3.12

6530| Cached filter refresh propagation across client source substitutions performance improvements

The above change should make sure that caching filters at a client org, will only cache it for that specific org.

Though when caching from the default org, it will cache all client orgs filters.

Does the above negate the need to enforce cache filters on demand?

Thanks,

David

Yes, the changes in the caching mechanism in 7.3.12 should take care of the problem we had.