In fact, just about anything you do working with routines is slow: renaming, deleting, compiling. Deleting a job or sequence incurs about the same performance.
I suspect that DS is doing some sort of full scan of the repository so that it can invalidate jobs that reference the job/routine you are deleting/compiling.
DS is on a dedicated stand-alone Unix server, and I am the only one logged into the server. This is not a resource contention issue. Look, I'll show you:
ps -ef | grep ds
Code: Select all
root 25678 1 0 Sep13 ? 00:00:01 /opt/Ascential/DataStage/DSEngine/bin/dsrpcd
c985675 30616 25678 0 00:40 ? 00:00:11 dscs 4 0 0
c985675 30617 30616 2 00:40 ? 00:02:23 dsapi_slave 7 6 0
c985675 31910 25678 0 01:57 ? 00:00:04 dscs 4 0 0
c985675 31914 31910 1 01:57 ? 00:00:29 dsapi_slave 7 6 0
c985675 32354 28222 0 02:26 pts/0 00:00:00 grep ds
Code: Select all
2:24am up 10 days 21:27, 1 user, load average: 0.21, 0.13, 0.10
It has been like this ever since we started with DS, although it is getting worse as our repository grows. We now have about 50 routines, 150+ server jobs, and 150+ job sequences.