X persons developing processes in K2 Studio

J
Badge +5

Hello,


I'm working on a project with a customer and currently we have a team of 5 persons working on their local desktops using K2 Studio to develop 5 different K2 processes (one process per person). Each guy has locally his K2 studio project file and then deploys to a K2 server that is running on a server box.


The issue is that we are experiencing several difficulties starting with the time a deploy takes, around 10min to complete a process deploy with more or less 12 activities and 30 or 40 events. Also, when one deploy starts the other 4 persons must wait until it finishes, attempting to make even 2 deploys simultaneous will fail on the 2nd one.


If we consider 5 persons working, then it takes about an hour for all of them be able to make a single deploy and then test it.


Any one is experiencing this kind of issues and is using any strategy to minimize it?


Thanks.

3 replies

N
Badge +8

Do they use virtual machines?


One of our teams, working on VMs, has the exact same problem. We went to the conclusion they should install the Blackpearl hostserver on each of their virtual machines, in order to have standalone MOSS + K2 + Visual Studio environments. However we fear it might come from the SQL Server.

J
Badge +5

Hi Nicolas,


Each person has its physical desktop machine, actually fairly good machines with 2 CPUs at 2Ghz and 2GB of memory.


The problem is the server box, one physical machine with 1 CPU at 3.2GHz and 8GB of memory hosting 3 Virtual machines


- 1 for K2, 1 for MOSS and 1 for SQLServer


Probably this is short on the server box, but this is customer configuration and the problem is knowing where is the bottleneck to be able to re-think the config.


On K2 projects having a team working in pararel this question should popup always, but this is our first project so no previous background to help

N
Badge +8

Yes we have quite the same situation here.


Just to share our experience, one of our developers stayed at the office late in the evening last month, and, it mustn't be a simple coincidence, as the network traffic was almost null and she was the only one working on the server, she was able to publish in a couple of minutes instead of 15 minutes.


Yet in your case, I agree that your host server is a little weak compared to the requirements (especially for SQL Server).

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings