search

valdisiljuconoks / localization-provider-opti

Database driven localization provider for Optimizely (ex. Episerver) websites
Apache License 2.0
11 stars 17 forks source link

Cache invalidation going nuts after upgrade to 8.x #220

Closed toregjerdrum closed 5 months ago

toregjerdrum commented 5 months ago

We released our Optimizely site on .NET 8 on 15.May. We upgraded all nugets as well, so we are running Optimizely on version 12.29.0 and DbLocalizationProvider on version 8.0.3. After the release, it looks like cache invalidation sends a lot of cache invalidation messages all the time.

We are running the site in Azure and have 4 instances of the app service. If we peek the messages on the topic, the messages that are there is from dblocalizationprovidercache. See the attached image to se the increased amount of messages on the Azure Service Bus. image

toregjerdrum commented 5 months ago

Not many changes done in the EPiServerCacheManager, but does this change make any sense?

toregjerdrum commented 5 months ago

A little update: We added our own EPiServerCacheManager where we removed the CacheManager.Remove(key) in the Insert metod. Now it looks good again. https://github.com/valdisiljuconoks/localization-provider-opti/blob/1173b6b80b2172c37324db15788eb4972280be99/src/DbLocalizationProvider.EPiServer/EPiServerCacheManager.cs#L13

valdisiljuconoks commented 5 months ago

stupid cache :)

valdisiljuconoks commented 5 months ago

should be normalized in v8.1.0

evest commented 5 months ago

New packages are in the Opti Nuget feed now.