salem@fritz.sri.com (Bruce B. Salem) (07/07/90)
The following is a piece of mail to mm-bug@columbia.edu that bounced. If you don't want to read the gory details, go to next message now! I profiled MM as it ran from a cliant machine in a network of Suns running SunOS 4.0.3 both on the server and cliant. On the server the startup is pretty quick, but on the client the startup takes 90 seconds before MM is ready. The server is running NFS and is the mail spooler. In this case fritz.sri.com is a diskless client of ginger.sri.com, the file and mail server. The profiling produces: fritz: /usr/ginger/salem> ll mon.out -rw------- 1 salem 252013 May 23 13:59 mon.out fritz: /usr/ginger/salem> prof /home/b/mm/mm %time cumsecs #call ms/call name 27.1 0.92 22 41.82 _getdents 10.0 1.26 42 8.10 _open 7.1 1.50 53 4.53 _mbox_rdmsg 4.7 1.66 36 4.44 _read 4.1 1.80 1738 0.08 _fgets 3.5 1.92 1709 0.07 _index 3.5 2.04 46 2.61 _ioctl 2.9 2.14 1739 0.06 _memccpy The getdents call reads directories in a portable way. The man page says that the directory(3) call should be used instead. I have seen 12 patches for MM. The sigon banner is: Columbia MM, version 0.88(7)-Beta This is a test version of MM. Please report all bugs by using MM's bug command, or just send mail to bug-mm. Suggestions are also welcome. Reading /usr/ginger/salem/mbox 53 messages read If you can suggest a fix or workaround or point me to someone who has, I would greatly appreciate it! Thank, You Bruce Salem