|o|... Mon, Sep 13, 1999 at 10:16:30AM -0300, Luiz Morte da Costa Junior ...|o| wrote:
>
> Hi list,
>
> I can't solve the problem yet.
>
> When I runnig the dmesg command, I have:
>
> ---
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <SEAGATE ST39140LW 1483> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> da1 at ahc0 bus 0 target 1 lun 0
> da1: <SEAGATE ST39140LW 1483> Fixed Direct Access SCSI-2 device
> da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing
> Enabled
> da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> ---
>
> I did a test, changing only the SCSI disk, using the same motherboard
> (L440GX+). I ran the dmesg command again and I received:
>
> --
> da0 at ahc0 bus 0 target 0 lun 0
> da0: <QUANTUM QM39100TD-SW N491> Fixed Direct Access SCSI-2 device
> da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing
> Enabled
> da0: 8683MB (17783250 512 byte sectors: 255H 63S/T 1106C)
> --
>
>
> I realized that the quantum disk have a 80.000MB/s transfers.
> Does someone use a SEAGATE ST39140LW disk and have I/O problems?
>
> Regards,
> Luiz Morte.
>
> PS:
> Someone told me that vipw doens't have much I/O disk, but when I run it
> with 12000 accounts, my disk have a lot off access.
da uma olhada se ele nao ta paginando, a geracao do dbm novo e'
rapida se vc disser para ele fazer tudo em ram, senao ele faz
em disco
O pwd_mkdb tem esta opcao para evitar isso:
-s cachesize
Specify in megabytes the size of the memory cache used by the hash-
ing library. On systems with a large user base, a small cache size
can lead to prohibitively long database file rebuild times. As a
rough guide, the memory usage of pwd_mkdb in megabytes will be a
little bit more than twice the figure specified here. The default
is 2 megabytes.
poe ai 16M e testa pra ver, o vipw que chama ele nao tem, vc pode
recompilar o pwd_mkdb c/ um default de 16M se for o caso
>
> On Sun, 22 Aug 1999, Luiz Morte da Costa Junior wrote:
> >
> > Hi all,
> >
> > I have a problem with a server running a FreeBSD 3.2.
> >
> > My Server has a L440GX+ Serber Board (intel), with network card 10/100,
> > SCSI AIC 7896 (80MB/s), 2 SCSI disk with 9GB (80MB/s), 2 pentium III
> > 450Mhz (not overclocked). The NIC and SCSI are onboard.
> >
> > I recompiled a kernel to SMP, and it worked. The server is ok, but when
> I
> > run a comand with disk access (whith vipw or mysql), the performance of
> > server goes down. My server stays very very very slow. If I use pine to
> > read my messages, it doesn't work. When the comand finishes, the server
> > stays "ok" again.
> >
> > I recompiled the kernel with "maxusers 128", but it doesn't work.
> >
> > My SCSI cable has a terminator and the scsi setup is ok (I think :) ).
> >
> > The dmesg command output is in attchmnt.
> >
> > I appreciate any help.
>
> []s,
>
> Luiz Morte da Costa Junior
> Analista de Redes E-mail: [EMAIL PROTECTED]
> Telefone: +55 19 754-2532 Fax: +55 19 255-7576
> CorreioNet - Correio Popular Campinas - SP - Brazil
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
.sig: license expired, contact your vendor
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
