Slow Deployments

Aaron Van

Are there any tips on why initial deployments would be so slow?

When you hit deploy and the bottom right corner is doing the little blue arrow flashing thing... what is going on?

Is that compiling anything or perhaps writing all the blobs to the database?

My Designer is now locking up for a solid 1-2 minutes after I hit deploy.

Any project that uses my library has this issue.

The library contains roughly 35 roles and 45 flags + 1 server side script.

Once the designer unlocks it gives you the two "Deployment Started" "Validating Metastorm Project PROJNAME" messages.

Then it will wait here for 30-45 seconds then do the deploy.

Now the 30-45 seconds I've seen since the begining of this project, but this locking up for 2 minutes is new.

Once the first deploy is complete, I can hit deploy again and it doesn't lock up... just does the 2 minute thing per normal.

Any ideas?

As a side note, I've only installed the Designer and not the engine, deployment service, etc... since I am deploying to a different environment. I'm running version 9.2 (9.3 also but I uninstalled in hopes of fixing) and other users with 9.1 SR2 are functioning as normal.

Find more posts tagged with

BPM

Comments

Brian Mellert

I don't have that kind of timing issue, and a I have more roles than that in one solution. I also have a designer only install on my PC since the engine / deployment services are on our engine server.

The blue blinky is saving to disk. Then it validates everything (I suspect that may be where your time is going). Then it starts to deploy to the database. There are usually messages scrolling during this portion. The prior portions, there usually aren't many messages (presuming validation passes).

Prakash__Kanchan

Designer is a well known memory hog - I'd check how much memory you have left on your local PC when the blue thing is flashing.

If you have limited RAM and there's all kinds of virtual memory paging going on at the same time designer is trying to save to disk - that couldconceptually slow things down.

Some other possiblities (if you have visual studio)

/awd/forums/questions/3402895

Kaman_Paul

I know after Designer "deploys" it updates eProcedure with the BLOB. It does this AFTER it tells you deployment is complete but you'll note the upload / deploy arrow blinking. We have seen this especially true when deploying remote. So if there is network latency, SQL Server is busy, etc, then the post deploy step ("blobifying the procedure") can take a while and actually fail.

Aaron Van

Thanks for all the tips so far.

I've seemed to isolate it to the web service connection in the library.

I created a new library with just roles and added it to a new solution. While a bit slower to deploy than no library, it still never locked up the Designer. Once I added the web service connection to the new library, deployed, and updated library in new solution. The deploy locked the designer for about 2 minutes before actually starting the deploy process.

Once the first deploy is done, it seems like any subsequent deploys have no issue. It almost feels like there is an authentication issue which resolves after first deploy allowing any further deploys to run smoothly.

Aaron Van

So now that I know it's the library and primarily the web service connection, where could this potentially affect the performance of the desiner? I'm now seeing a 30 second lag when clicking the 'When action completed' event editor. I know this is an impossible question to answer. I'm just hoping maybe someone else has experienced something like this and has found the root cause.

achopra

how much RAM do you have on your machine? as Prax mentioned earlier, the Designer chews up a lot of memory so you will need a good amount of free memory to run smoothly. I also recommend a fast processor and an SSD.

Aaron Van

Nah, it's not that.. I havea 8GB ram + ssd and an i7.

I wouldn't pay much mind to this thread any more since it would be impossible to diagnose without providing web service logs and such. Thanks for the help.