Let me first say, I am not a expert progress DBA. I do have some knowledge, but I am looking here for some direction.
Currently we run progress 9.1. Will be upgrading to 10.1 soon, but I'm first having to look at some performance issues.
We run a program called SX enterprise on top of progress. The reason I mention that is because of the table names.
We run both progress and SXe on an IBM AIX system. Most of the Progress tables are on a 2 gig fibre channel disk subsystem.
1st. users will say the system is moving slow. As an example they will show us their screen as they type in characters. Usually they'll hit the key and it'll take a second to appear on the screen.
2nd. When we notice that happening, we'll fire up topas and notice that hdisk10 will be anywhere between 80-90% busy.
On our system, hdisk10 is mounted under db_area1 on the disk subsystem.
In that directory are numerous data files
ie.
nxt_30.d#
nxt_50.d#
nxt_107.d#
Well after some research it seems that the highest activity table in that directory is
nxt_107.d1
This is from the schema file
/db_area1/nxt_107.d1 f 2000000
/db_area1/nxt_107.d2 f 2000000
/db_area1/nxt_107.d3 f 2000000
/db_area1/nxt_107.d4
From speaking with others about this problem, there are about 3 schools of thought on what size those files should be and on what disk they should be distributed on. None of which I full understand.
If anyone has any suggestions on how to better configure these files for better performance, I would appreciate it.
Thanks in advance and I can provide any additional information as needed.
Kevin
Currently we run progress 9.1. Will be upgrading to 10.1 soon, but I'm first having to look at some performance issues.
We run a program called SX enterprise on top of progress. The reason I mention that is because of the table names.
We run both progress and SXe on an IBM AIX system. Most of the Progress tables are on a 2 gig fibre channel disk subsystem.
1st. users will say the system is moving slow. As an example they will show us their screen as they type in characters. Usually they'll hit the key and it'll take a second to appear on the screen.
2nd. When we notice that happening, we'll fire up topas and notice that hdisk10 will be anywhere between 80-90% busy.
On our system, hdisk10 is mounted under db_area1 on the disk subsystem.
In that directory are numerous data files
ie.
nxt_30.d#
nxt_50.d#
nxt_107.d#
Well after some research it seems that the highest activity table in that directory is
nxt_107.d1
This is from the schema file
/db_area1/nxt_107.d1 f 2000000
/db_area1/nxt_107.d2 f 2000000
/db_area1/nxt_107.d3 f 2000000
/db_area1/nxt_107.d4
From speaking with others about this problem, there are about 3 schools of thought on what size those files should be and on what disk they should be distributed on. None of which I full understand.
If anyone has any suggestions on how to better configure these files for better performance, I would appreciate it.
Thanks in advance and I can provide any additional information as needed.
Kevin