Skip to main content
To homepage To homepage
Solved

Repository Compute Tier (v20.x)

sierd.zuiderveld
Contributor
Forum|alt.badge.img+1

What would be the recommended compute tier for a project's repository database? (TX v20.x) 

I believe the current default on Azure is General Purpose 2vCores, however looking at the utilization this seems to be excessive. 

Does anyone have experience with running the repository on a Standard DTU database? 

Thx

Best answer by wouter.goslinga

Hi @sierd.zuiderveld , I commonly use a Standard 20 DTU database for the repository. This works fine, even for larger projects with several thousands of versions:

 

 

View original

wouter.goslinga
TimeXtender Xpert
Forum|alt.badge.img+2

Hi @sierd.zuiderveld , I commonly use a Standard 20 DTU database for the repository. This works fine, even for larger projects with several thousands of versions:

 

 

sierd.zuiderveld
1 person likes this
  • sierd.zuiderveld
    sierd.zuiderveld
rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • July 13, 2023

Hi,

while 20 DTU is a good starting point (until the DTU model disappears) I disagree with: "This works fine, even for larger projects with several thousands of versions:” . There are three parameters that define repository responsiveness:

  • number of objects in project (the export size of the xml is a proxy for this)
  • number of changes in repository
  • amount of execution logging held in the repository database

You will generally notice slowness creeping in as these parameters grow. But really that isn't something to worry about as the whole point of PaaS databases is that you can scale them as required. However, if you know you are going to need the resource for a year or longer you can get substantial cost reductions from reserved capacity. Reserved Capacity is not available in the DTU model.

Reply


Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings