Latest attempt pasted below, with HOSTLOWMEM 3, REQUEST OFF and FAILREFARGSFLOOR
0.1%r. Bottom line: no change in time; still more than 5 hours.
In my next trial, I'm going to set all the *LOWMEM commands to 3, just to see the
effect. Any other suggestions to try? No portion of the latest report seems overly
long.
Stephen originally suggest that my long run times were due to the system thrashing;
that's how I started with the LOWMEM commands. Is there any other way to increase the
memory allocation for this program in Unix? I don't think 'nice' has anything to do
with this. Any compiler options? Anything I'm not thinking of?
Thanks for your suggestions.
-Kevin
Command being timed: "/opt/analog/analog-5.32/analog
+g/opt/analog/conf.d/wwwinfo.analog.cfg"
User time (seconds): 1426.31
System time (seconds): 740.86
Percent of CPU this job got: 10%
Elapsed (wall clock) time (h:mm:ss or m:ss): 5:31:57
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 0
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3222935
Minor (reclaiming a frame) page faults: 1571733
Voluntary context switches: 0
Involuntary context switches: 0
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------
