How should Perforce VCS roots be configured in TeamCity for large repositories? -

this question identical this one, related perforce instead of svn. in perforce have these branches:

development\projecta\trunk  development\projecta\release1 development\projecta\release2 

in teamcity should there 3 separate vcs roots or 1 checkout rules specified each build?

following advice of accepted answer in linked question changed our setup have single vcs root contain everything. performance dire initial checkout taking 45 minutes.

the build configurations set checkout server side , have checkout rules such as:

-:. +:development/projecta/trunk  

i'm worried setup isn't scalable. if 3 branches takes 45 minutes, few more releases , checkout time prohibitive. best practice setting perforce vcs roots large repositories in teamcity?

after contacting jetbrains support, answer:

the checkout rules not efficient perforce , server-side checkout, have separate issue performance problem, cannot tell id right now. right now, server side checkout, teamcity checks out whole vcs root , after filters necessary data according checkout rules.

the solutions problem be:

• use checkout on agent. teamcity perform agent-side checkout efficiently, creating dedicated perforce workspace vcs root configuration , checkout rules.
• use checkout on server, use dedicated vcs root configurations.