Over the weekend we were running a bulk import of 75 million records, we had scaled up cosmos to meet the demand of this but it kept on being scaled down. We worked out that it was scaling down every time our application restarted - or more specifically the cosmos storage engine was initalised.
builder.UseCollection(x => x.CollectionRequestUnits = 500);
builder.UseDatabase(x => x.DatabaseRequestUnits = 500);
From experience with the cosmos SDK, I'd have only expected these values to be used at provisioning time. If the desire is to have these values used every time, then I'd expect that the value should only be used to scale up cosmos, rather than scale down.
Over the weekend we were running a bulk import of 75 million records, we had scaled up cosmos to meet the demand of this but it kept on being scaled down. We worked out that it was scaling down every time our application restarted - or more specifically the cosmos storage engine was initalised.
From experience with the cosmos SDK, I'd have only expected these values to be used at provisioning time. If the desire is to have these values used every time, then I'd expect that the value should only be used to scale up cosmos, rather than scale down.