DISKIO - updated version in need of TEST

[roberto]

Hmm, seems like low CPU score, what are you running? If that's a fast CPU I think we may be getting an overflow in the benchmark code, on my TO-DO list.

This is a old laptop hp8760w with xeon

So CPU is an 8-core chip, yes?

Yes

Can you get me a debug-run on just that drive please?

This disk1 is a 1tb sdd, but show 114470mb

Code: [Select]

DISKIO - Fixed Disk Benchmark, Version 1.25
(C) 1994-1998 Kai Uwe Rommel
(C)      2004 madded2
    2020-2024 Dariusz Piatkowski

Number of fixed disks: 10
Number of CD-ROM drives: 2

Dhrystone 2.1 C benchmark routines (C) 1988 Reinhold P. Weicker
Dhrystone benchmark for this CPU: 3308172 runs/sec

 DEBUG => using DosPhysicalDisk for $1:

 DEBUG => found the disk...

 DEBUG => sectors is : 63
 DEBUG => tracks  is : 14593
 DEBUG => sides   is : 255
 DEBUG => sector  is : 512

Hard disk 1: 255 sides, 14593 cylinders, 63 sectors per track = 114470 MB

Drive cache/bus transfer rate: 101216 k/sec

 DEBUG => nSector  is: 512
 DEBUG => nSectors is: 63
 DEBUG => nData    is: 521773056
 DEBUG => nTime    is: 5155

Data transfer rate on cylinder 0      : 115738 k/sec

 DEBUG => nData is: 594897408
 DEBUG => nTime is: 5140

Data transfer rate on cylinder 14591  : 241781 k/sec

 DEBUG => nData is: 1239372288
 DEBUG => nTime is: 5126

CPU usage by full speed disk transfers: 0%
Average latency time: 0.1 ms

 DEBUG => nTime is: 1
 DEBUG => nCnt is: 33782

Average data access time: 0.1 ms

 DEBUG => nTime is: 1
 DEBUG =>  nCnt is: 37410


Multithreaded disk I/O
1  thread: 116244 k/sec, 0% CPU usage

 DEBUG => nTotal is: 596800512
 DEBUG => nTime is: 5134

2 threads: 109120 k/sec, 0% CPU usage

 DEBUG => nTotal is: 559351296
 DEBUG => nTime is: 5126

3 threads: 108347 k/sec, 0% CPU usage

 DEBUG => nTotal is: 556254720
 DEBUG => nTime is: 5134

4 threads: 109145 k/sec, 0% CPU usage

 DEBUG => nTotal is: 560899584
 DEBUG => nTime is: 5139

5 threads: 108745 k/sec, 0% CPU usage

 DEBUG => nTotal is: 560254464
 DEBUG => nTime is: 5152

6 threads: 111054 k/sec, 0% CPU usage

 DEBUG => nTotal is: 571931136
 DEBUG => nTime is: 5150

7 threads: 111081 k/sec, 0% CPU usage

 DEBUG => nTotal is: 571737600
 DEBUG => nTime is: 5147

8 threads: 110371 k/sec, 0% CPU usage

 DEBUG => nTotal is: 566318592
 DEBUG => nTime is: 5131


Yup, USB devices...I am looking at ways of checking whether the storage devices that are identified by DISKIO at the start are actually usable, before the attempt to benchmark them actually starts.

The disk3 is no disk, no usb conected.

Saludos

[Martin Iturbide]

Hello

Subsequently, I now present you with DISKIO v1.25 (http://darcio.no-ip.org/os2/diskio/diskio-v1.25-Dec_2024.zip),

Just to be part of the fun, I also wanted to test it out.
I tried it here on a VirtualBox ArcaOS 5.1 Guest machine running on a Windows 10 host.

I run diskio.exe >out.txt

It has:

Code: [Select]

DISKIO - Fixed Disk Benchmark, Version 1.25
(C) 1994-1998 Kai Uwe Rommel
(C)      2004 madded2
    2020-2024 Dariusz Piatkowski

Number of fixed disks: 9
Number of CD-ROM drives: 2

Dhrystone 2.1 C benchmark routines (C) 1988 Reinhold P. Weicker
Dhrystone benchmark for this CPU: 6045508 runs/sec

Hard disk 1: 255 sides, 5221 cylinders, 63 sectors per track = 40954 MB

Drive cache/bus transfer rate: 92707 k/sec
Data transfer rate on cylinder 0      : 54160 k/sec
Data transfer rate on cylinder 5219   : 313296 k/sec
CPU usage by full speed disk transfers: 12%
Average latency time: 0.2 ms
Average data access time: 0.8 ms

Multithreaded disk I/O
1  thread: 41534 k/sec, 11% CPU usage

Hard disk 2: 12 sides, 512 cylinders, 9 sectors per track = 27 MB

Drive cache/bus transfer rate: Disk read error.
Data transfer rate on cylinder 0      : Disk read error.
Data transfer rate on cylinder 510    : Disk read error.
CPU usage by full speed disk transfers: Disk read error.
Average latency time: Disk read error.
Average data access time: Disk read error.

Multithreaded disk I/O
1  thread:
and it gave me this error:

SYS1808:
The process has stopped.  The software diagnostic
code (exception code) is  009B.

I will try it on real hardware later.

Regards