Set Progress DB .PF file
- Thread starter rainylsh
- Start date
RealHeavyDude
Well-Known Member
You don't mention your Progress/OpenEdge version, the type of database license ( workgroup or enterprise ), and what your database block size is. This is important information.
AFAIK, the -inp parameter is a client parameter that's ignored when supplied to start a database, plus, I think that's true for the -rand parameter too ...
Overall, to me this looks like a parameter file which mixes client and database startup parameters.
In general: Although it is possible to give catch-all advises - for example to increase the buffer pool is very often a good thing. But it's not one magic button and you need to proceed carefully step by step. For example when you increase the buffer pool you might run into problems with buffer flushes during checkpoints. Therefore you should analyze your performance problems in the first place and then take actions.
Heavy Regards, RealHeavyDude
AFAIK, the -inp parameter is a client parameter that's ignored when supplied to start a database, plus, I think that's true for the -rand parameter too ...
Overall, to me this looks like a parameter file which mixes client and database startup parameters.
In general: Although it is possible to give catch-all advises - for example to increase the buffer pool is very often a good thing. But it's not one magic button and you need to proceed carefully step by step. For example when you increase the buffer pool you might run into problems with buffer flushes during checkpoints. Therefore you should analyze your performance problems in the first place and then take actions.
Heavy Regards, RealHeavyDude
this is my .st file. as i know, the block size is 8k
it's enterprise,Progress version is 9.1D.
According to Progress help file, I set the -B = (8 * users) 2 = (8 * 40) 2 = (8 * 35)2 = 78400 ~ 80000
#
b r:\dtsd.b1
#
d "Schema Area":6,64 r:\dtsd.d1 f 512000
d "Schema Area":6,64 r:\dtsd.d2 f 512000
d "Schema Area":6,64 r:\dtsd.d3 f 512000
d "Schema Area":6,64 r:\dtsd.d4 f 512000
d "Schema Area":6,64 r:\dtsd.d5 f 512000
d "Schema Area":6,64 r:\dtsd.d6 f 512000
d "Schema Area":6,64 r:\dtsd.d7 f 512000
d "Schema Area":6,64 r:\dtsd.d8 f 512000
d "Schema Area":6,64 r:\dtsd.d9 f 512000
d "Schema Area":6,64 r:\dtsd.d10 f 512000
d "Schema Area":6,64 r:\dtsd.d11 f 512000
d "Schema Area":6,64 r:\dtsd.d12 f 512000
d "Schema Area":6,64 r:\dtsd.d13 f 512000
d "Schema Area":6,64 r:\dtsd.d14 f 512000
d "Schema Area":6,64 r:\dtsd.d15 f 512000
d "Schema Area":6,64 r:\dtsd.d16 f 512000
d "Schema Area":6,64 r:\dtsd.d17 f 512000
d "Schema Area":6,64 r:\dtsd.d18 f 512000
d "Schema Area":6,64 r:\dtsd.d19 f 512000
d "Schema Area":6,64 r:\dtsd.d20 f 512000
d "Schema Area":6,64 r:\dtsd.d21 f 790400
d "Schema Area":6,64 r:\dtsd.d22 f 512000
d "Schema Area":6,64 r:\dtsd.d23 f 512000
d "Schema Area":6,64 r:\dtsd.d24 f 512000
d "Schema Area":6,64 r:\dtsd.d25 f 617600
d "Schema Area":6,64 r:\dtsd.d26 f 512000
d "Schema Area":6,64 r:\dtsd.d27 f 512000
d "Schema Area":6,64 r:\dtsd.d28 f 512000
d "Schema Area":6,64 r:\dtsd.d29 f 1255808
d "Schema Area":6,64 r:\dtsd.d30 f 512000
d "Schema Area":6,64 r:\dtsd.d31 f 512000
d "Schema Area":6,64 r:\dtsd.d32 f 512000
d "Schema Area":6,64 r:\dtsd.d33 f 2097024
d "Schema Area":6,64 r:\dtsd.d34 f 512000
d "Schema Area":6,64 r:\dtsd.d35 f 512000
d "Schema Area":6,64 r:\dtsd.d36 f 512000
d "Schema Area":6,64 r:\dtsd.d37
it's enterprise,Progress version is 9.1D.
According to Progress help file, I set the -B = (8 * users) 2 = (8 * 40) 2 = (8 * 35)2 = 78400 ~ 80000
#
b r:\dtsd.b1
#
d "Schema Area":6,64 r:\dtsd.d1 f 512000
d "Schema Area":6,64 r:\dtsd.d2 f 512000
d "Schema Area":6,64 r:\dtsd.d3 f 512000
d "Schema Area":6,64 r:\dtsd.d4 f 512000
d "Schema Area":6,64 r:\dtsd.d5 f 512000
d "Schema Area":6,64 r:\dtsd.d6 f 512000
d "Schema Area":6,64 r:\dtsd.d7 f 512000
d "Schema Area":6,64 r:\dtsd.d8 f 512000
d "Schema Area":6,64 r:\dtsd.d9 f 512000
d "Schema Area":6,64 r:\dtsd.d10 f 512000
d "Schema Area":6,64 r:\dtsd.d11 f 512000
d "Schema Area":6,64 r:\dtsd.d12 f 512000
d "Schema Area":6,64 r:\dtsd.d13 f 512000
d "Schema Area":6,64 r:\dtsd.d14 f 512000
d "Schema Area":6,64 r:\dtsd.d15 f 512000
d "Schema Area":6,64 r:\dtsd.d16 f 512000
d "Schema Area":6,64 r:\dtsd.d17 f 512000
d "Schema Area":6,64 r:\dtsd.d18 f 512000
d "Schema Area":6,64 r:\dtsd.d19 f 512000
d "Schema Area":6,64 r:\dtsd.d20 f 512000
d "Schema Area":6,64 r:\dtsd.d21 f 790400
d "Schema Area":6,64 r:\dtsd.d22 f 512000
d "Schema Area":6,64 r:\dtsd.d23 f 512000
d "Schema Area":6,64 r:\dtsd.d24 f 512000
d "Schema Area":6,64 r:\dtsd.d25 f 617600
d "Schema Area":6,64 r:\dtsd.d26 f 512000
d "Schema Area":6,64 r:\dtsd.d27 f 512000
d "Schema Area":6,64 r:\dtsd.d28 f 512000
d "Schema Area":6,64 r:\dtsd.d29 f 1255808
d "Schema Area":6,64 r:\dtsd.d30 f 512000
d "Schema Area":6,64 r:\dtsd.d31 f 512000
d "Schema Area":6,64 r:\dtsd.d32 f 512000
d "Schema Area":6,64 r:\dtsd.d33 f 2097024
d "Schema Area":6,64 r:\dtsd.d34 f 512000
d "Schema Area":6,64 r:\dtsd.d35 f 512000
d "Schema Area":6,64 r:\dtsd.d36 f 512000
d "Schema Area":6,64 r:\dtsd.d37
TomBascom
Curmudgeon
9.1D is, of course, ancient, obsolete and unsupported. You should upgrade.
Beyond that -- RHD is right there is no simple magical answer. Performance tuning is hard work. To do it right you have to measure various performance metrics and understand what they are telling you.
None the less some advice can be offered.
0) Your problem, if you have one (you have not described an actual problem), may not be related to database settings. It may very well be client settings. In particular you are using -H and -S. If this is a character app (or there are app servers) and everything is on the same physical server get rid of these. If you need to keep them then you also need to be explicitly setting -Mn, -Ma, -Mi and, possibly, some others.
1) You say that you have an Enterprise license. The #1 "silver bullet" available to you is to set -spin 10000. Just do it and say "thank you".
2) -B should usually be as big as you can make it without causing a RAM shortage. With 8k db blocks, 4GB of RAM and a 32 bit system that will be about 500,000. That works out to 2GB (because a 32 bit system is limited to 2GB of shared memory).
3) All of your data is in the schema area. The next biggest bang for the buck is to fix that. Create storage areas and put all of your tables and indexes into those storage areas based on the average record size and the level of activity for the table (index areas should just correspond to data areas). NO data should be in the schema area.
4) The .pf file is only part of the puzzle. You should also be starting a BIW, an AIW (you do have after-imaging enabled? right?), 2 APWs and WDOG. You should also have the bi cluster size set to a non-default value. 16384 is "a good start".
5) Get some professional help.
Beyond that -- RHD is right there is no simple magical answer. Performance tuning is hard work. To do it right you have to measure various performance metrics and understand what they are telling you.
None the less some advice can be offered.
0) Your problem, if you have one (you have not described an actual problem), may not be related to database settings. It may very well be client settings. In particular you are using -H and -S. If this is a character app (or there are app servers) and everything is on the same physical server get rid of these. If you need to keep them then you also need to be explicitly setting -Mn, -Ma, -Mi and, possibly, some others.
1) You say that you have an Enterprise license. The #1 "silver bullet" available to you is to set -spin 10000. Just do it and say "thank you".
2) -B should usually be as big as you can make it without causing a RAM shortage. With 8k db blocks, 4GB of RAM and a 32 bit system that will be about 500,000. That works out to 2GB (because a 32 bit system is limited to 2GB of shared memory).
3) All of your data is in the schema area. The next biggest bang for the buck is to fix that. Create storage areas and put all of your tables and indexes into those storage areas based on the average record size and the level of activity for the table (index areas should just correspond to data areas). NO data should be in the schema area.
4) The .pf file is only part of the puzzle. You should also be starting a BIW, an AIW (you do have after-imaging enabled? right?), 2 APWs and WDOG. You should also have the bi cluster size set to a non-default value. 16384 is "a good start".
5) Get some professional help.
Similar threads
