Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
Hi, Just want to know whether it is normal: A process (SYMBIONT_00n) running OA$FORMATTER.EXE image will be of base priority 7 and chew much CPU time. Our client system performance has been very poor after upgrading ALL-IN-1 to V3.0. Lot of actions have been taken in the VMS level: e,g. memory related system parameter adjusted using AUTOGEN, disk reorganisation using BACKUP/RESTORE. However, for the CPU problem, it has been found almost 100% utilized. The above mentioned process is one of the top CPU time chewer. Is it a normal situation? Could the priority of the kind of process be lowered? To what extent will this affect the ALL-IN-1 system? OA$FORMATTER image will consume much CPU time? Any idea? Thanks Alex
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3091.1 | Proportional spacing = Disproportionate CPU time | IOSG::CHINNICK | gone walkabout | Fri Jul 30 1993 11:50 | 21 |
Alex, you might see in some of the topics discussing performance in this conference that the Formatter in ALL-IN-1 V3.0 is from WPS-PLUS V4 and supports proportional spacing. This makes it chew CPU time. I certainly can't recommend running it above user priorities unless you have a CPU to dedicate to running it! Check the queue priority using $ SHOW QUEUE/FULL OA$FORMATTER and it should show the /BASE_PRIORITY which the queue is running at. You should be able to change this using INIT/QUEUE or SET QUEUE specifying /BASE_PRIORITY. I'd suggest a value of 4 since that is the normal interactive priority. BTW, an earlier note also suggested increasing the KOA$HEAP_SIZE value as a way of speeding up the formatter, but watch out for the extra page-faults and working-set you might require. Paul. |