Skip to main content

Azure DevOps–Why is my database so big?

When preparing an Azure DevOps Server migration, the customer asked me why there Azure Devops databases grew so fast.

There are 2 queries that can help you answer this question.

  • The first query gives a general overview of the different parts:

The output of the first query returned the following results in this case:

Owner BlobSizeInMb
VersionCVersionControl 64992.008339881835
FileContainer 59599.479797363281
TeamTest 44243.018857001953
WorkItemTracking 23674.237445831054
CodeSense 989.945262908203
ProcessTemplate 125.949053763671
Generic 54.288738250000
  • The second query goes in more detail to differentiate between source control and build:

The output of the second query returned the following results in this case:

FileContainerOwner TotalSizeInMb
Build 56681.754142760742

Git

 875.809092521484

vstfs:///Rele

 683.627062796875

pipelines://b

 271.543574333007

DistributedTask

 1.143143653320

They started storing there build artifacts in the database, this explained why there Azure DevOps databases exploded so much.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more