Improve performances
Improve performances
How is possible to improve the performaces of the ControlM server and EM ?
In a new linux machine installtion with oracle I have a veery slow response: a single job that do an ls command duration is about 15 minutes, slow to start, that yellow for many time and finally green.
I know that there is a manner to configure the use of temporaries directories in a ram, like ramdrive in win. But how and for witch folders?
Thanks
In a new linux machine installtion with oracle I have a veery slow response: a single job that do an ls command duration is about 15 minutes, slow to start, that yellow for many time and finally green.
I know that there is a manner to configure the use of temporaries directories in a ram, like ramdrive in win. But how and for witch folders?
Thanks
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
Hy mauriziog,
you've just to download TunningCTM6.1.03SOLARIS-SYBASE.pdf on the download part of the site (Controlm server).
All is explain about it:
the FS are the following :
in 6.1.03
$HOME/ctm/tmp
$HOME/ctm/pid
in 6.3
$HOME/ctm_server/tmp
$HOME/ctm_server/pid
just create them in tmp directorie by
mkdir -p /tmp/ctm/pid
mkdir -p /tmp/ctm/tmp
chown group:user /tmp/ctm/pid
chown group:user /tmp/ctm/tmp
delete tmp and pid directories in $HOME/ctm
and do the following links:
ln -s /tmp/ctm/pid pid
ln -s /tmp/ctm/tmp tmp
you've just to download TunningCTM6.1.03SOLARIS-SYBASE.pdf on the download part of the site (Controlm server).
All is explain about it:
the FS are the following :
in 6.1.03
$HOME/ctm/tmp
$HOME/ctm/pid
in 6.3
$HOME/ctm_server/tmp
$HOME/ctm_server/pid
just create them in tmp directorie by
mkdir -p /tmp/ctm/pid
mkdir -p /tmp/ctm/tmp
chown group:user /tmp/ctm/pid
chown group:user /tmp/ctm/tmp
delete tmp and pid directories in $HOME/ctm
and do the following links:
ln -s /tmp/ctm/pid pid
ln -s /tmp/ctm/tmp tmp
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
the swap is declared at installation of the host , but it's remove at every boot of the host. So the swap is recreate at every boot, and your own links have to be declared as a static process in the rcx.d directories (as following example)
DEV root@vega:/etc/rc2.d # more S51Controlmserver
# create tmp directories in swap
mkdir -p /var/run/ctm/pid
mkdir -p /var/run/ctm/tmp
chown ctm630d:ctm630 /var/run/ctm/pid
chown ctm630d:ctm630 /var/run/ctm/tmp
cd /prj/bcm/dev/ctm630d/ctm_server
ln -s /var/run/ctm/pid pid
ln -s /var/run/ctm/tmp tmp
# start database at boot
su - ctm630d -c dbversion
if [ $? -eq 0 ] ; then
echo "SQL Server is already running "
exit 15
else
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/startdb ]; then
echo "Starting SQL server for CONTROL-M"
su - ctm630d -c startdb &
echo "Sleeping for 20"
sleep 20
fi
fi
# start CONTROL-M Configuration Agent at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca ]; then
echo "Starting CONTROL-M Server Configuration Agent"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca &
sleep 10
fi
# start CONTROL-M at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm ]; then
echo "Starting CONTROL-M application"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm &
sleep 10
fi
exit 0
DEV root@vega:/etc/rc2.d #
this example works correctly at every reboot of this host
regards
Philmalmaison
DEV root@vega:/etc/rc2.d # more S51Controlmserver
# create tmp directories in swap
mkdir -p /var/run/ctm/pid
mkdir -p /var/run/ctm/tmp
chown ctm630d:ctm630 /var/run/ctm/pid
chown ctm630d:ctm630 /var/run/ctm/tmp
cd /prj/bcm/dev/ctm630d/ctm_server
ln -s /var/run/ctm/pid pid
ln -s /var/run/ctm/tmp tmp
# start database at boot
su - ctm630d -c dbversion
if [ $? -eq 0 ] ; then
echo "SQL Server is already running "
exit 15
else
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/startdb ]; then
echo "Starting SQL server for CONTROL-M"
su - ctm630d -c startdb &
echo "Sleeping for 20"
sleep 20
fi
fi
# start CONTROL-M Configuration Agent at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca ]; then
echo "Starting CONTROL-M Server Configuration Agent"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca &
sleep 10
fi
# start CONTROL-M at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm ]; then
echo "Starting CONTROL-M application"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm &
sleep 10
fi
exit 0
DEV root@vega:/etc/rc2.d #
this example works correctly at every reboot of this host
regards
Philmalmaison
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
the swap is declared at installation of the host , but it's remove at every boot of the host. So the swap is recreate at every boot, and your own links have to be declared as a static process in the rcx.d directories (as following example)
DEV root@vega:/etc/rc2.d # more S51Controlmserver
# create tmp directories in swap
mkdir -p /var/run/ctm/pid
mkdir -p /var/run/ctm/tmp
chown ctm630d:ctm630 /var/run/ctm/pid
chown ctm630d:ctm630 /var/run/ctm/tmp
cd /prj/bcm/dev/ctm630d/ctm_server
ln -s /var/run/ctm/pid pid
ln -s /var/run/ctm/tmp tmp
# start database at boot
su - ctm630d -c dbversion
if [ $? -eq 0 ] ; then
echo "SQL Server is already running "
exit 15
else
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/startdb ]; then
echo "Starting SQL server for CONTROL-M"
su - ctm630d -c startdb &
echo "Sleeping for 20"
sleep 20
fi
fi
# start CONTROL-M Configuration Agent at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca ]; then
echo "Starting CONTROL-M Server Configuration Agent"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca &
sleep 10
fi
# start CONTROL-M at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm ]; then
echo "Starting CONTROL-M application"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm &
sleep 10
fi
exit 0
DEV root@vega:/etc/rc2.d #
this example works correctly at every reboot of this host
regards
Philmalmaison
DEV root@vega:/etc/rc2.d # more S51Controlmserver
# create tmp directories in swap
mkdir -p /var/run/ctm/pid
mkdir -p /var/run/ctm/tmp
chown ctm630d:ctm630 /var/run/ctm/pid
chown ctm630d:ctm630 /var/run/ctm/tmp
cd /prj/bcm/dev/ctm630d/ctm_server
ln -s /var/run/ctm/pid pid
ln -s /var/run/ctm/tmp tmp
# start database at boot
su - ctm630d -c dbversion
if [ $? -eq 0 ] ; then
echo "SQL Server is already running "
exit 15
else
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/startdb ]; then
echo "Starting SQL server for CONTROL-M"
su - ctm630d -c startdb &
echo "Sleeping for 20"
sleep 20
fi
fi
# start CONTROL-M Configuration Agent at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca ]; then
echo "Starting CONTROL-M Server Configuration Agent"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ca &
sleep 10
fi
# start CONTROL-M at boot
if [ -f /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm ]; then
echo "Starting CONTROL-M application"
su - ctm630d -c /prj/bcm/dev/ctm630d/ctm_server/scripts/start_ctm &
sleep 10
fi
exit 0
DEV root@vega:/etc/rc2.d #
this example works correctly at every reboot of this host
regards
Philmalmaison
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
You could find RAMDISK in the download part of the site.
That version run correctly with Windows 2003 and Control-M.
So, the result was not so important than Unix Swap memory usage.
You need a lot of available memory.
Windows already use DISK to extend its own memory.
Concerning the CLUSTER version.
I don't know. Anyway, be carefull to use only temporary files in RAMDISK.
You won't have any lost files during th switch.
That version run correctly with Windows 2003 and Control-M.
So, the result was not so important than Unix Swap memory usage.
You need a lot of available memory.
Windows already use DISK to extend its own memory.
Concerning the CLUSTER version.
I don't know. Anyway, be carefull to use only temporary files in RAMDISK.
You won't have any lost files during th switch.
Hi fyot,
For the CLUSTER: the temporary files is exactly the problem.
If the ramdrive can be clusterizable maybe we dont lose the temporary files on switch...
I think that in the cluster environment is not advisable.
Dont you?
Thanks for this informations about performances, good and usefull feedback.fyot wrote:So, the result was not so important than Unix Swap memory usage.
You need a lot of available memory.
Windows already use DISK to extend its own memory.
Concerning the CLUSTER version.
I don't know. Anyway, be carefull to use only temporary files in RAMDISK.
You won't have any lost files during th switch.
For the CLUSTER: the temporary files is exactly the problem.
If the ramdrive can be clusterizable maybe we dont lose the temporary files on switch...
I think that in the cluster environment is not advisable.
Dont you?