We’re showing data from a CosmosDb in a table with pagination. The underlying query is using grouping along with OFFSET and LIMIT.

We’re showing data from a CosmosDb in a table with pagination. The underlying query is using grouping along with OFFSET and LIMIT.

In my ASPCoreNet using entity framework, I have a database of Record:

Let’s say that I have a document of the following structure.

I’m designing a system that stores customer telemetry data on a daily basis. My index format is “TenantId:date”, such as “tenant1:2024-09-01”, and the item is a large JSON blob containing all telemetry data for that day.

I’m using the CosmosDB Linux emulator in a Docker container on WSL2. I’m connecting from a .NET Core app (in Windows or WSL2).

Does anybody know why our Cosmos DB is not scaling high enough even though Normalized RU is continuously at 100% for a couple of hours.

my first instinct was to think that I must fundamentally misunderstand something about CosmosDB on Azure but I don’t know what that would be in this case. How can I possibly go beyond the autoscale 1000RU/s of this account on 40 RU when my partition keys are set to random values (=partition key is by user id which is a guid)?

I am trying to design a cosmos db which I am showing below. In my json format below, the majority of items will be uploaded once, then the nested item of “Trades”, will be once per day. In “Trades”, I will have a reference to another container of “price”, which will be updated every few seconds.

I am trying to design a cosmos db which I am showing below. In my json format below, the majority of items will be uploaded once, then the nested item of “Trades”, will be once per day. In “Trades”, I will have a reference to another container of “price”, which will be updated every few seconds.