4ge using up too much processor time
Posted in 1999
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL
I have discovered a 4gl program while seems to be slowing down our system as it is using a lot of processor time. After running for a few hours it had used about 25 seconds of processor time and was growing. Every other process had used very little processing time. We are running Online 5.08 on SCO Openserver 5.04 with 256 Mb Ram with 2 pentium pro processors. I believe that something may be wrong as the program should not demand so much processor time. The program does select a lot of data and creates temp tables. I realise that this is not much to go on but I am looking for ideas for things to chek for in the code which may be standard things to check for e.g. closing cursors. In fact is this normal anyway ? could it just be the case that the nature of the program will mean that it will use up a lot of CPU time?
You are worried about 25secs of CPU usage over several hours? No! CPU usage is not the problem. I would look elsewhere. Get and run TOP for your platform and monitor other applications (top shows the top N processes by resource usage, cpu by default) and memory usage. Perhaps some process' memory image is growing over time and forcing the system to thrash swap. Tam McLaughlin wrote: > > I have discovered a 4gl program while seems to be slowing down our > system as it is > using a lot of processor time. After running for a few hours it had used > about 25 seconds of processor time and was growing. Every other process > had used very little processing time. > We are running Online 5.08 on SCO Openserver 5.04 with 256 Mb Ram with 2 > pentium pro processors. I believe that something may be wrong as the > program should not demand so much processor time. The program does > select a lot of data and creates temp tables. I realise that this is not > much to go on but I am looking for ideas for things to chek for in the > code which may be standard things to check for e.g. closing cursors. In > fact is this normal anyway ? could it just be the case that the nature > of the program will mean that it will use up a lot of CPU time?