How many processes are run in the background and approximately how much CPU cycle time do they take?
WorkPace forks to run two processes when it is run. The first is the GUI and application itself, the second process is for grabbing input events. It communicates the input events to the main program with sockets. When WorkPace is running using the X “record” extension, CPU usage for the input program is minimal, since input is given to us via callbacks, the program is sleeping when the user is not typing. Testing on a 270MHz Sun Ultra 5 running Solaris 8 showed that the GUI program can sometimes reach usage of 3-4% when updating the status panel and the floating icon. If lower CPU usage is required, both the status panel and floating icon animation can be turned off, which caused WorkPace to use around 1% CPU time.