Page 1 of 1
Node configuration
Posted: Wed Sep 12, 2007 9:45 am
by rao_2004
Hi,
we are trying to add more space to one of the project on a Aix server.Here our main goal is to utilize the new space or new mountpoint for this specific project in performance view.
i mean do i have to edit the config file or just change the dataset or txt file path in environment level.
Is their any better way in utilising the space for the specific project..
Thanks,
rao..
Posted: Wed Sep 12, 2007 10:48 am
by Kirtikumar
There can be many ways to utilize it. Few which I can think of:
If you are creating temp files, you can create them in this space.
If the AIX is SMP machine, then just changing the dataset file path for one of the nodes and the new space would be used.
Posted: Wed Sep 12, 2007 11:05 am
by rao_2004
You mean,i have to to pass parameter $APT_CONFIG_FILE for all jobs that are developed for the project and point at the disk space.
Posted: Wed Sep 12, 2007 1:56 pm
by kwwilliams
Only if you want them to be able to run on more than the default configuration file. (Which you will at some point want the ability to dial a job up or down without effecting every job in your project.)
Posted: Mon Sep 17, 2007 3:17 pm
by rao_2004
Say for ex If i want to use 100 GB for specific project ABC and i want to run all jobs in specific project ABC on 4 or 6 nodes for more performance.
This is the way i'm following,please correct me if i doing some thing wrong or is their better way:
1.Create a config file for the Project ABC and using $APTCONFIG parameter in all ABC Projects jobs.
2.Node file:
node "node1"
{
fastname "dev"
pools ""
resource disk "/apps/ascential/tst/dspara/ABC/node1/datasets" {pools ""}
resource scratchdisk "/apps/ascential/tst/dspara/ABC/node1/scratch" {pools ""}
}
Added another 3 nodes like to the config file.
Posted: Mon Sep 17, 2007 10:25 pm
by Raghavendra
I believe it should be okay to proceed.Lets see what our DSGurus comment on this.
Posted: Mon Sep 17, 2007 11:15 pm
by ArndW
Each and every job has a node configuration at which it will run best, and this is seldom the maximum number of nodes. By "best" I don't necessarily mean fastest, this could mean 'fastest speed and smallest footprint'.
You can use two basic methods to control your runtime node allocations:
a) different config files as you have already mentioned
b) use one configuration file but within that and the jobs use nodepools.