# of uvsh.exe s running

PilotBaha · Post by **PilotBaha** » Thu May 20, 2004 4:01 pm

Is it normal to have more uvsh.exe running than the # of jobs. We had some "hung" jobs and looking at the Win Task Manager the we see 10 uvsh.exe s even though we are running only 2 DS jobs..

ray.wurlod · Post by **ray.wurlod** » Thu May 20, 2004 4:51 pm

It's not abnormal.

For example, a job with multiple active stages may start a separate process for each active stage, as well as the controlling process that is actually running the job.

Connected clients may also temporarily use uvsh processes, for example when compiling.

DeepakCorning · Post by **DeepakCorning** » Thu Aug 11, 2005 3:58 pm

Does it means that if i have 10 stages in one job then may haapen that for that job 10 uvsh.exe s will be called??

If yes then what are then ways to reduce it or something like that as if i want to run many job at a same time i will be loading the server with many number of exes and making it too slow.

ray.wurlod wrote:It's not abnormal.

For example, a job with multiple active stages may start a separate process for each active stage, as well as the controlling process that is actually running the job.

Connected clients may also temporarily use uvsh processes, for example when compiling.

chulett · Post by **chulett** » Thu Aug 11, 2005 5:14 pm

The number of Active stages are the key here, not the total number of stages in the job. And Ray did say that they may start separate processes, it depends on your job design (amongst other things).

DeepakCorning · Post by **DeepakCorning** » Fri Aug 12, 2005 8:04 am

I got that chulett what I said was IT MAY happen that a job may trigger 10 exes and as u say it depends on the job design, What i like to know what are the standars or ways to reduce this means like keep the transaction size low and all.

chulett wrote:The number of Active stages are the key here, not the total number of stages in the job. And Ray did say that they may start separate processes, it depends on your job design (amongst other things).

ray.wurlod · Post by **ray.wurlod** » Fri Aug 12, 2005 5:54 pm

The number of uvsh processes has no effect whatsoever on the transaction size, which is a property in the stage that actuallky loads the database table.
The number of uvsh processes is solely a function of the number of active stages in the job and how these are connected to each other (and, perhaps, whether you are using row buffering).