marwood@ncs.dnd.ca (Gordon Marwood) (12/08/89)
We will shortly be installing 386/ix for the first time (on a Honeywell-Bull 386). The recommended minimum memory is 2MB. I would be interested to hear about recommendations for memory size, and its practical effect on performance of 386/ix. I realize that this depends a lot on the way in which the machine is used. All I can say about our projected use is that it will be used for mail by a group of, perhaps 20 people, though I suspect no more than 6 at a time. We also expect to use it as a file server for the same group, using NFS. I suppose that the closest comparison might be with someone who has used 386/ix on a similar machine (20 MHz) for a similar group size. Gordon Marwood Internet: marwood@ncs.dnd.ca
jgd@rsiatl.UUCP (John G. De Armond) (12/09/89)
In article <710@ncs.dnd.ca> marwood@ncs.dnd.ca (Gordon Marwood) writes: >We will shortly be installing 386/ix for the first time (on a >Honeywell-Bull 386). The recommended minimum memory is 2MB. I would be >interested to hear about recommendations for memory size, and its >practical effect on performance of 386/ix. I realize that this depends >a lot on the way in which the machine is used. All I can say about our >projected use is that it will be used for mail by a group of, perhaps 20 >people, though I suspect no more than 6 at a time. We also expect to >use it as a file server for the same group, using NFS. I suppose that >the closest comparison might be with someone who has used 386/ix on a >similar machine (20 MHz) for a similar group size. Don't even think of starting with less than 8 MB for a group that size. I've run 386/ix with 2, 4, and 8 meg and the transformation at each stage is awsom. This machine is used for development by 2 people, news reading by a few more and handles a very heavy news redistribution load. With 2 people logged in and any kind of news processing going on in the background, the 4 MB machine paged rather badly. When we upgraded to 8 meg, the personality of the machine changed markedly. Even when the system is not paging, it is much more responsive. Note: I have done no tuning on this system. The kernal is configured exactly as shipped and/or as kconfig builds it. With 20 users I presume you are connecting these in through an Ethernet? I hope so. 4 or 5 users on TTY logins is pushing it pretty far on this 20 mhz machine. If you are installing Ethernet, you must use an intelligent card such as the Interlan unit supported by ISC. I've used this card and can report that it performs very well. In general, you want to avoid creating interrupts on the PC bus. I've determined that it is almost essential to have intelligence in anything that handles a datastream. The configuration here is a no-name klone 20 mhz 386 with 8 mb of 80 ns RAM running 0 wait state. The drive controller is an Adaptec 1272 SCSI adaptor with floppy interface (Recommended!). Video is a mono graphics board (slow). Serial interfaces consist of an 8 port intelligent card from StarGate (highly recommended) and a single PC-type async card with a 16550 uart (mandatory!) Hard drive configuration is a high speed CDC Wren 40 meg drive for the root partition and 2 380 MB Newbury Data SCSI drives (Trash, but cheap at the time.) The Wren is run from a fast ST-506 AT controller. Tape backup is a Wangtek 60 mb unit. Slow but reliable. I HIGHLY recommend a separate drive for the root partition. I spent many miserable days reinstalling from floppies after one disk problem or the other before I put a stone cold reliable root drive on the system. Unless you have at least 2 physical drives, almost any reconfiguration of the file system mandates going back to floppies. One further comment on the Stargate board. This board and the company behind it has been fantastic. I have an older 8 bit interface version, though they make a 16 bit interface one. With the performance I've seen, I really can't imagine a pressing need for the 16 bit one. My initial test of the board consisted of setting up 8 simultaneous cats of a large file to each of the 8 ports at 38.4 kilobaud. SAR reported a CPU idle time of 98%! I verified with a protocol analyzer that the pipe was being kept full on all ports. In practical use, I can now force handshaking on all my Telebit feeds downstream even one using the Bell smart card. I run zmodem transfers at 38.4 kb between a PC and the system with no problems at all. The installation went perfect. Set a couple of dip switches on the board and tell the installation script these settings and let it rebuild a kernal. I called tech support with a minor question (800 number) and was serviced by a very knowledgable person who helped me immediately. An additional note. The manual documents how to write applications to run on the 80186 coprocessor on the board. The firmware is loaded as pump code when you go to run state 2. Since the board uses Z80 SIO equivelents and since each port has full modem control and all handshake lines, all kinds of communications processing applications ideas arise. At the least, one could program the thing to answer the phone and output a "system down" message when dialin is not available. One should also note that this board can be run in polled mode if you don't have a spare interrupt. I tried it polled and found performance to be below that of interrupt-driven service. I suspect tuning would solve that problem but since I had a spare interrupt, I just flipped a switch. One thing I noted in the manual is that all shared memory mapping is done by the pump code and that multiple boards can share the same shared memory segment. Very nice when high memory segments are getting tight as in my system. My only complaints are that the manuals are fairly poor, with the Unix section being an addendum to the DOS/Generic version and the fact that they charge $50.00 for additional system drivers. If you wanna use it on Xenix or DOS too, that's extra money. Minor quibbles. I didn't mean for this to turn into a Stargate commercial but it's so rare to run into quality support in the PC Unix field, I thought a positive note for a change would be welcome. BTW, after working with Stargate and their vendor-supported driver, I'm suddenly glad that Interactive is shoving driver support off to the vendors. Knowledgable service is refreshing. John -- John De Armond, WD4OQC | The Fano Factor - Radiation Systems, Inc. Atlanta, GA | Where Theory meets Reality. emory!rsiatl!jgd **I am the NRA** |
mcneild@spock (Doug McNeil) (12/10/89)
In article <710@ncs.dnd.ca> marwood@ncs.dnd.ca (Gordon Marwood) writes: >We will shortly be installing 386/ix for the first time (on a >Honeywell-Bull 386). The recommended minimum memory is 2MB. I would be >interested to hear about recommendations for memory size, and its >practical effect on performance of 386/ix. I realize that this depends >a lot on the way in which the machine is used. All I can say about our >projected use is that it will be used for mail by a group of, perhaps 20 >people, though I suspect no more than 6 at a time. We also expect to >use it as a file server for the same group, using NFS. I suppose that >the closest comparison might be with someone who has used 386/ix on a >similar machine (20 MHz) for a similar group size. We have been using 386/ix for approximately a year. We are a developement shop but I believe our experience is germain. We run a number of 386 systems which range from a 16MHZ machine with an 80MB ST506 and 4MB to a 25MHZ machine with a 360MB ESDI and 8MB. We run TCP/IP and NFS on all of them. I can catagorically state that you wouldn't want to run NFS on a machine with 2MB even if it were possible. _Size_ gives the following for our kernel: 590184 + 101012 + 585136 = 1276332 Our 16MHZ machine is used in a test environment. Some of the software we test on it is large enough to lead to significant swapping even though it is used in _single_user_ mode. If you just want to use your system for mail it is possible that 2MB might suffice. For any significant NFS work 4MB would be required and 8MB plus would be nice. -- ------------------------------------------------------------------------------> "Smokin" Doug McNeil | uunet!mitel!spock!mcneild Mitel Corporation, Kanata, Ontario | (613)592-2122 "Got any dragons you need slain?" RAH |
greyham@hades.OZ (Greyham Stoney) (12/12/89)
in article <828@rsiatl.UUCP>, jgd@rsiatl.UUCP (John G. De Armond) says: > With 20 users I presume you are connecting these in through an Ethernet? > I hope so. 4 or 5 users on TTY logins is pushing it pretty far on this > 20 mhz machine. If you are installing Ethernet, you must use an intelligent > card such as the Interlan unit supported by ISC. I've used this card and > can report that it performs very well. In general, you want to avoid > creating interrupts on the PC bus. I've determined that it is almost > essential to have intelligence in anything that handles a datastream. Make sure you get the Intelligent card though. The Interlan NI5210 (which is a "dumb" card) does NOT work with NFS; we've tried and tried, and always met with failure. We haven't tried the intelligent card (as John evidently has, with much success); all I can say is that the NI5210 don't work. Interactive have confirmed this as follows: % From pyramid!oliveb!ism780c!ism780b!386ixsup@murtoa.cs.mu.oz Thu Nov 23 19:36:39 1989 % Date: Wed, 22 Nov 89 14:37:09 pst % From: 386/ix Support <386ixsup@ism780b.oz> % Message-Id: <8911222237.AA04225@ism780b.isc.com> % To: greyham@hades.seg.ausonics.nucleus.oz % Subject: Re: NFS problems % % There are known problems running NFS with that particular % ethercard. The problem was in Interlan's TCP driver. They % have forwarded a new driver to us that fixes several such % problems, but which is so slow as to be impractical. They % are now trying to resolve that issue. % % In sum, we suggest any other card than the NI5210. Greyham. -- /* Greyham Stoney: Australia: (02) 428 6476 * * greyham@hades.oz - Ausonics Pty Ltd, Lane Cove, Sydney, Oz. * * ISDN: Interface Subscribers Don't Need */
martin@mwtech.UUCP (Martin Weitzel) (12/12/89)
In article <1629@mcneild> mcneild@mcneild (Doug McNeil) writes: [some stuff deleted] >If you just want to use your system for mail it is possible that 2MB might >suffice. For any significant NFS work 4MB would be required and 8MB plus would >be nice. Regarding the low memory prices, I'd not recommend to use 386/ix with less then 4MB, though it runs with 2MB. I've used it this way in the beginning and could never understand, why people did tell great storys about it - it seemed incredible slow to me. Then, after upgrading to 4MB, things changed dramatically! FYI: I'm the only user on a ACER S/32-20, ESDI-Disk (140MB), neither NFS, nor X11; frequently compiling and using ELAN's 'eroff'. Except for the documentation (which is promised to get better with 2.2) I'm rather content with my configuration. Martin Weitzel
lee@sq.sq.com (Liam R. E. Quin) (12/15/89)
This article includes a lot of random thoughts on configuring 386/ix, and some thoughts/experience on choosing a memory size. My understanding is that the Honeywell-Bull (now Bull) 386 machine is actually based on the Acer 1100 system. This may not be true outside the UK, and may not even be true there any more. In the following, though, I'll assume that it is true. You could find out by looking at the motherboard, of course, but one of the reasons for posting is so we find out [0.5 :-)]. > marwood@ncs.dnd.ca (Gordon Marwood) writes: >> We will shortly be installing 386/ix for the first time (on a >> Honeywell-Bull 386). The recommended minimum memory is 2MB. For more than six users doing you will want at least 4 megabytes of RAM. If they are not using GNU emacs, and are not using the C compiler, this may suffice, particularly with an intelligent I/O board. I have seen eight or so word-processor users on a 16 MHz 386 doing just fine with 4MBytes of (32-bit-slot fast) RAM. The disk and RAM speed is more important than the quantity on this sort of machine. >> All I can say about our >> projected use is that it will be used for mail by a group of, perhaps 20 >> people, though I suspect no more than 6 at a time. If that is all they are doing, a Digiboard or an Acer Smart board (I think that this is what Bull use) will be fine. >> We also expect to >> use it as a file server for the same group, using NFS. I suppose that >> the closest comparison might be with someone who has used 386/ix on a >> similar machine (20 MHz) for a similar group size. If your purchasing dept. and/or budget is sufficiently flexible, you could start with 2 Meg and expand later if you need to. Check before you do that the system you buy has the larger chips, as otherwise you may have to throw away your first 2 Meg in order to expand! It is worth having a fully expanded motherboard, though, if you can afford it. John G. De Armond (jgd@rsiatl.UUCP) writes: > Don't even think of starting with less than 8 MB for a group that size. > I've run 386/ix with 2, 4, and 8 meg and the transformation at each > stage is awsom. This machine is used for development by 2 people, news > reading by a few more and handles a very heavy news redistribution load. > With 2 people logged in and any kind of news processing going on in the > background, the 4 MB machine paged rather badly. When we upgraded to > 8 meg, the personality of the machine changed markedly. Even when the > system is not paging, it is much more responsive. Of course, using a machine for development and for reading mail are rather different. For X-windows you *must* have 8 or more Megabytes of RAM or you will quickly go insane go insane go insane go insa Otherwise, less is fine. > Note: I have done no tuning on this system. The kernal is configured > exactly as shipped and/or as kconfig builds it. It is *really* worth whil going through kconfig. Configure the HPDD (this will make sense when you run kconfig -- select 7), configure the system to use the default parameters for mamory size, choose the facilities and drivers you want (as few as possible!), and rebuild. In particular, do not install any of the Xenix stuff from the distribution floppies. Configuring for memory parameters can double performance. And if you are using nfs, you may want to increase most of the STREAMS parameters, as described in the System Administration Guide. > With 20 users I presume you are connecting these in through an Ethernet? > I hope so. S board such as Specialix (Acer 1100/20 only not 1100/25), Digiboard or Corollary will be quite happy. For 20 users I suggest Specialix or the Corollary, and if you are using modems, avoid the boards (like the Corollary 8x8, Chase and others) which don't give full 6- or (better) 8-wire modem flow control. With host-based tcp/ip, NFS will keep the system busy, so either use the Interlan board (check it is supported at the appropriate release) which I have not had a chance to try yet, or the excelan board (excellent, but their 386/ix suppor is poor). It is better to use a serial card than ethernet if you have host-based tcp/ip, becasue this reduces the number of interrupts the CPU will get. > 4 or 5 users on TTY logins is pushing it pretty far on this > 20 mhz machine. I disagree strongly with this! (unless you use a dumb serial board) > If you are installing Ethernet, you must use an intelligent > card such as the Interlan unit supported by ISC. I've used this card and > can report that it performs very well. In general, you want to avoid > creating interrupts on the PC bus. I've determined that it is almost > essential to have intelligence in anything that handles a datastream. But I *do* agree with this (as already indicated) > The configuration here is a no-name klone 20 mhz 386 with 8 mb of 80 ns > RAM running 0 wait state. The drive controller is an Adaptec 1272 SCSI > adaptor with floppy interface (Recommended!). The Adeptec SCSI card is well worth the extra over the Future Domain, if you have the choice (based on limited knowledge, however). I have used only the AHA1540S, not the 1272. The fastest SCSI disks I have seen are the CDC Wrens, at 10.7ms... And they are quite cheap, too. Micropolis and Priam are other candidates, to list but two... > Video is a mono graphics > board (slow). This is relative. The Acer board is actually one of the faster ones, and some of them also emulate Hercules graphics (not the default board shipped with the 1100/20, however). > Serial interfaces consist of an 8 port intelligent card > from StarGate (highly recommended) and a single PC-type async card with > a 16550 uart (mandatory!) If you only get five serial users, that would be a good reason *not* to buy this card as far as I can see.... I wonder what I have misunderstood? > Hard drive configuration is a high speed > CDC Wren 40 meg drive for the root partition and 2 380 MB Newbury > Data SCSI drives Well, what do you know? :-) I suggest booting from the SCSI disk, however. Also, don't buy disks from Bull if you can help it! They charge a fortune... > a fast ST-506 AT controller. Tape backup is a Wangtek 60 mb unit. Slow > but reliable. The nicest tape drive I've used with 386/ix was the Archive Viper (SCSI). Very, very fast, even with /bin/tar it moves continuously. If you can't use the Viper, the Wangtek is reasonably reliable, although I did see some data suggsting Tandberg (Tandburg?) was better. The wangtek goes quite fast with pdtar (or gnu tar if you are not a commercal outfit or don't mind being infected with the Gnu Public License). [sorry, couldn't resist a bit of politics :-) :-)] If you can't get hold of ptar, use tar cvfb - usr (or wherever) | dd obs=500k of=/dev/tape and it will go about 20 times faster (or it seems to...) I couldn't get the Wangtek working with the Acer 1100/25, but I didn't try for very long. I imagine that Bull would use the Cypher drive, which has a plastic slide that comes out of the drive about a centimetre, and a handle one rotates in order to load the tape in place. Again, this goes fastest with dd or pdtar. > I HIGHLY recommend a separate drive for the root partition. I spent > many miserable days reinstalling from floppies after one disk problem > or the other before I put a stone cold reliable root drive on the system. > Unless you have at least 2 physical drives, almost any reconfiguration > of the file system mandates going back to floppies. Actually it isn't too much of a drag to go back to floppies, as long as * you make several (not just one) copies of the boot/install diskette, and try them out!!! * you copy (with mount and cpio) the files from the boot diskette onto a directory on your hard disk, so that you can understand the INSTALL script. > One further comment on the Stargate board. This board and the company > behind it has been fantastic. [...] > initial test of the board consisted of setting up 8 simultaneous > cats of a large file to each of the 8 ports at 38.4 kilobaud. SAR > reported a CPU idle time of 98%! I verified with a protocol analyzer > that the pipe was being kept full on all ports. In practical use, > I can now force handshaking on all my Telebit feeds downstream even one > using the Bell smart card. I run zmodem transfers at 38.4 kb between > a PC and the system with no problems at all. So maybe the board *is* good, and you could have more than 5 logins? > The installation went perfect. Set a couple of dip switches on the board > and tell the installation script these settings and let it rebuild > a kernal. I called tech support with a minor question (800 number) > and was serviced by a very knowledgable person who helped me immediately. In order to get the Acer 1100/25 to work reliably with the Adaptec board, I found it necessary to adjust the bus timing dip switches to increase the delay. Then the systems passed saok testing with no problems. With the serial board in place, you might have to disable the cache (from CMOS setup), which turns out to have less effect than expected but is still irritating. If you have enough memory (say, 16 Meg), you could try experimenting with a RAM disk. Also, an 80387 makes a difference. Note that (at least on the 1100/25) the jumpers on the motherboard indicating presence or absence of a floating-point chip are labelled incorrectly! The labels are reversed. Symptoms of getting them wrong include the /etc/dfspace at login time either hanging or giving wildly incorrect results, SoftQuad's SQPS output not printing on PostScript, Elan troff dumping core, and xeyes & xclock behaving totally wrongly. Since the operating system is compiled to use an 80387, a weitek will not speed up the operating system or utilities -- only programs you write. Hence, it is not worth the extra cost unless you are doing a lot of development. > BTW, after working with Stargate and their vendor-supported driver, I'm > suddenly glad that Interactive is shoving driver support off to the > vendors. Knowledgable service is refreshing. Well, I have always found Interactive very helpful, but then I deal with Interactive Ltd. in Britain. Also, a couple of hints if you are not to be the only adminstrator: * change the ends of /etc/rc0 and /etc/rc1 -- echo "the system is down" must be changed to echo "please wait. Do not switch off yet." because if you switch off between "the system is down" and "press any key to reboot", you will lose your hard disk. All of it. Bye bye. And if you have a cacheing disk controller, wait another minute. This is my only really major gripe with 386/ix. * order the full documentation set, including the Prentice Hall manuals. You will need them, especially as 386/ix does not come with on-line man pages (although there is a reasonable "help"). * the default sendmail.cf is not very helpful. You might want to replace sendmail with smail or something. But hacking mailers is neither pleasant nor rewarding, and the only consolation is that is is less un-fun than hacking uucp.... and less fun but easier than hacking troff :-) :-) I run elm under 386/ix with few problems. Hope this helps a little. These notes are all my own thoughts, not my employer's... Feel free to mail/phone if you want. Lee -- Liam R. Quin lee@sq.com (a visitor, not an employee) until Dec 20th. -- +1 416 963 8337 (visiting Canada) After then -- +44 565 50021 (work, in Knutsford, UK, 10:00-19:00 GMT), or +44 925 831084 (home; please, please no calls outside 07:30...01:00 GMT!!!)
martin@mwtech.UUCP (Martin Weitzel) (12/17/89)
In article <1989Dec15.043544.19508@sq.sq.com> lee@sq.com (Liam R. E. Quin) writes: [many lines deleted] >* the default sendmail.cf is not very helpful. You might want to replace > sendmail with smail or something. But hacking mailers is neither I also had a lot of struggle with ISC's "sendmail" until someone (here in the newsgroups) pointed out, that one should try to run the installation- script "/usr/lib/mail.install". Doing so solved all my problems. Thanks to the poster! There is one minor flaw in this scripts, that requires you must manually delete the (upper case) 'U' from the flags (F=....) in the "Mlocal"-Line. after the installation. (Running the scripts requires, that you are familiar with terms like "relay host", "domain" aso., but I think that could be assumed from someone, who wants to link his or her machine into an UUCP-Net.) [rest deleted] -- <<< MW -- email: see header -- voice: 49-(0)6151-6 56 83 >>>