JSON serialization not working with Hybrid configuration

[gordon-matt]

I was trying to use JSON serialization instead (as mentioned here: #253). But it throws an exception like: InvalidOperationException: Sequence contains no matching element.

This is my setup:

services.AddEasyCaching(option =>
{
    option.UseInMemory("Memory");

    option.WithJson("JsonSerialization"); // Store as JSON, so we don't need to mark everything with [Serializable]

    // distributed
    option.UseRedis(config =>
    {
        config.DBConfig.Endpoints.Add(new ServerEndPoint("127.0.0.1", 6379));
        config.SerializerName = "JsonSerialization";
        //config.DBConfig.Database = 5;
    }, "Redis");

    // combine local and distributed
    option.UseHybrid(config =>
    {
        config.TopicName = "test-topic";
        config.EnableLogging = true;

        // specify the local cache provider name after v0.5.4
        config.LocalCacheProviderName = "Memory";
        // specify the distributed cache provider name after v0.5.4
        config.DistributedCacheProviderName = "Redis";
    }, "Hybrid")
    .WithRedisBus(busConf =>
    {
        busConf.Endpoints.Add(new ServerEndPoint("127.0.0.1", 6380));
    });
});

It works perfectly if I don't have the WithJson("JsonSerialization") and config.SerializerName = "JsonSerialization".

[catcherwong]

@gordon-matt Thanks for your interest in this project.

InvalidOperationException: Sequence contains no matching element.

Could you show us more details about this exception? such as the StackTrace.

It works perfectly if I don't have the WithJson("JsonSerialization") and config.SerializerName = "JsonSerialization".

Which version are you using? If you specify the SerializerName of a provider, the provider will this this serializer.

[gordon-matt]

Thanks for your reply.

I am using the latest NuGet versions: 1.4.1

I created a small test project for you.. : EasyCachingExample

Note: It works with CSRedis, which I have now configured it for (see Startup.cs).. but StackExchange Redis has an error (I commented out the configuration for that, but you can uncomment it (and comment CSRedis config) to test it..

Something else more important to note:

1. For some reason, StackExchange Redis is EXTREMELY slow.. unacceptably slow.. It took 4.2 mins to run the tests.. the worst was 1.4 minutes just for one operation: to insert about 20 items in the cache.

2. CSRedis is much faster, but it seems there is some initial setup happening that makes it always take about 8 seconds for the first time something is read or written and less than 1 second to complete all tests after that. Total time for all tests is less than 9 seconds.

You can run the tests and compare both versions to see what happens (how long it takes).

3. Even CSRedis is too slow. I inherited a project to work on which is very messy coding.. and I was hoping to use EasyCaching instead of the custom messy caching we have.. but even though it's messy, it still runs a bit faster than your CSRedis package. So I have just tidied up the code instead of using EasyCaching. If you want, I can see about extracting it for you and putting it in the example project I linked to above.. maybe you can improve yours by seeing what's happening there.

[catcherwong]

For CSRedis.

I have run the tests for your example by switching to .net6 due to I do not install .net5.

dotnet test .\EasyCachingExample.Tests.csproj for three times.

Visual Studio 2022 for once.

It seems that both of them are cost less than 1 second.

[catcherwong]

For StackExchange Redis

The StackTrace tell us that the redis bus can not find out the serializer, to solve this one, update the config in WithRedisBus

   在 System.Linq.ThrowHelper.ThrowNoMatchException()
   在 System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate)
   在 EasyCaching.Bus.Redis.DefaultRedisBus..ctor(String name, IEnumerable`1 subscriberProviders, RedisBusOptions busOptions, IEnumerable`1 serializers)
   在 EasyCaching.Bus.Redis.RedisBusOptionsExtension.<AddServices>b__3_1(IServiceProvider x)
   在 Autofac.Extensions.DependencyInjection.AutofacRegistration.<>c__DisplayClass3_0.<Register>b__0(IComponentContext context, IEnumerable`1 parameters)
   在 Autofac.Core.Activators.Delegate.DelegateActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)
   在 Autofac.Core.Activators.Delegate.DelegateActivator.<ConfigurePipeline>b__2_0(ResolveRequestContext ctxt, Action`1 next)
   在 Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   在 Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   在 Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(ResolveRequestContext context, Action`1 next)
   在 Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.<>c__DisplayClass14_0.<BuildPipeline>b__1(ResolveRequestContext ctxt)
   在 Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(ResolveRequestContext context, Action`1 next)

Also I run the test after uncommenting.

using dotnet test

using Visual Studio

1 second as well

[gordon-matt]

Great that it works faster in .NET 6. That is good news. I cannot update to .NET 6 yet though, because I am waiting for some other things to have issues fixed that prevents the upgrade. It's interesting though.. why it's slow with .NET 5? I wouldn't have thought there should be such a difference in speed just because of the target framework. Also thanks for the explanation to add Serializer Name in the bus as well. I will come back to look at EasyCaching again when I update to .NET 6. For .NET 5, you might want to either fix the speed problem or update the README to say there are problems in .NET 5 and recommend only .NET 6.

Anyway, thanks for your time

[catcherwong]

I run the example in a computer that installed .net 5 sdk.

Here is the test result.

Both of them work well.

Hope this one can help you out.

[gordon-matt]

That is really strange. I have no explanation then why the exact same code on mine takes so long, even though our own implementation (with StackExchange Redis) is super fast. I may have to investigate further. Thanks for your time anyway.