Error on regular usage

[Damian89]

Hey guys,
within my docker setup I used for dev, everythings fine.

Now I wanted to replace redis on a real (big) project and encountered the following in production:

10::47::27 crit: Session[0] [194.13.80.217:6379] [127.0.0.1:31726] [00B7AB7B] ProcessMessages threw an exception: Tsavorite.core.TsavoriteException: Entry does not fit on page    at Tsavorite.core.TsavoriteKV`2.CreateNewRecordUpsert[Input,Output,Context,TSessionFunctionsWrapper](Key& key, Input& input, Value& value, Output& output, PendingContext`3& pendingContext, TSessionFunctionsWrapper sessionFunctions, OperationStackContext`2& stackCtx, RecordInfo& srcRecordInfo) in /root/garnet/libs/storage/Tsavorite/cs/src/core/Index/Tsavorite/Implementation/InternalUpsert.cs:line 362    at Garnet.server.StorageSession.SET[TContext](SpanByte& key, SpanByte& value, TContext& context) in /root/garnet/libs/server/Storage/Session/MainStore/MainStoreOps.cs:line 295    at Garnet.server.GarnetApi`2.SET(SpanByte& key, SpanByte& value) in /root/garnet/libs/server/API/GarnetApi.cs:line 93    at Garnet.server.RespServerSession.NetworkSETEX[TGarnetApi](Byte* ptr, Boolean highPrecision, TGarnetApi& storageApi) in /root/garnet/libs/server/Resp/BasicCommands.cs:line 434    at Garnet.server.RespServerSession.ProcessMessages() in /root/garnet/libs/server/Resp/RespServerSession.cs:line 322    at Garnet.server.RespServerSession.TryConsumeMessages(Byte* reqBuffer, Int32 bytesReceived) in /root/garnet/libs/server/Resp/RespServerSession.cs:line 228

It sounds like a config error, maybe I need to adjust parameters but no idea where to start.

Any recommendations?

[Damian89]

Worth mentioning, that it works when using the following settings:

dotnet run -c Release -f net8.0 -- -i 512m -m 2050m --port 6379 --password XXX -p 128m -s 2g --obj-memory 128m --obj-page 3m --obj-segment 128m --obj-index 64m

But I dont know it this is smart, are there any recommendations where/how to start optimizing everything?

[badrishc]

Page size is configured based on the maximum value you might insert. The -p being larger would have allowed it to succeed.