On Thursday 23 January 2003 5:40 am, Noah Garrett Wallach wrote:
> On Wed, 22 Jan 2003, Dax Eckenberg wrote:
> > > so what exactly does KB per transaction mean? what happens if I am
> > > handling 300 concurrent users with 160Kbit encoded audio streams -
> > > could I in fact do this on this machin
On Wed, 22 Jan 2003, Dax Eckenberg wrote:
> >
> >
> > so what exactly does KB per transaction mean? what happens if I am
> > handling 300 concurrent users with 160Kbit encoded audio streams - could I
> > in fact do this on this machine? or will I be limited by the 64KB/t
> > issue?
> >
>
> 300 x
> > > I currently have an IDE drive that has the capacity to do 128KB/t and
> > > a SCSI drive 64KB/t. Are these stats in fact showing me that there
> > > is a limitation with the SCSI drive? Are my file transfering
> > > capaibilities less with the SCSI drive? I suppose what do I need to
> > >
>
> > I currently have an IDE drive that has the capacity to do 128KB/t and
> > a SCSI drive 64KB/t. Are these stats in fact showing me that there
> > is a limitation with the SCSI drive? Are my file transfering
> > capaibilities less with the SCSI drive? I suppose what do I need to
> > look for
In the last episode (Jan 22), Noah Garrett Wallach said:
> can somebody give me a better understanding of what the iostat output
> is decribing in the KB/t column. It might be really simple but
> figured I';d ask, if in fact further clarification can be given.
>
> typhoon% iostat 1
> tty
Hi,
can somebody give me a better understanding of what the iostat output is
decribing in the KB/t column. It might be really simple but figured I';d
ask, if in fact further clarification can be given.
typhoon% iostat 1
tty da0 da1 acd0
tin tout KB/t
