Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
113 user(s) are online (77 user(s) are browsing Forums)

Members: 2
Guests: 111

amigait, orgin, more...

Headlines

Forum Index


Board index » All Posts (Rolar)




Re: NVMe device driver
Just popping in
Just popping in


@geennaamQuote:
I actually just did the performance analysis

My result is ~85MB/s with NTFS. This is way slower than SFS2.
The net write speed isn't that all bad at ~500MB/s. But still only 1/3th of SFS2.

Thank you for your analysis :)! Your results are anyway in line with those I got. My Kingston NV2 is not the fastest model and does not have DDR4 cache, so I think it's normal if your Samsung shows somewhat better values.

Quote:
As I understand it, AmigaOS4 includes a port of NTFS-3G which has to go through an additional library called FUSE/FileSysBox. The sources are available in the download section of Hyperion (login required). So if anyone has some spare time and motivation to find out where the 100ms+400ms command delay for those two reads comes from then feel free to do so

I wish I had the skills for that...;).

Quote:
EDIT: I suppose that Linux on your X5040 will use all 4 cores when performing that benchmark. Unlike SFS2, NTFS-3G gives a 100% CPU load. So this is also a factor to consider when comparing NTFS results.

That's true... By default Linux uses the NTFS driver in kernel, but there is also a separate NTFS-3G driver. The advantage of the latter is that it allows to use 'fstrim' on NTFS partitions, but you have to mount the partion on fstab for it to work. There is also the newer NTFS3 driver (in kernel) but that is broken in PPC kernels.

The CPU load was very low (in average < 10%/core) when I tested a NTFS partition with 'Disks' tool. It seems that the AmigaOS NTFS-3G driver indeed needs some further work...

EDIT: Have you tried the SCSITools on your X5000? So far the only reference results I have seen are from Sailor and she has a X1000. It is said to have much better memory management, so the results cannot be directly compared with X5000.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@joergQuote:
C:Copy with 16 MB buffer is faster than SCSISpeed with 10 and 100 MB ones!? That's even more strange than your SCSISpeed results (SATA HD faster than SATA SSD). SCSISpeed only uses reads, while C:Copy does reads + writes, i.e. has to transfer twice as much data, and with the slow CPU memory speed I wouldn't be surprised at all if RAM: is slower than a partition on a NVMe.

Edit: Or did you calculate the C:Copy speeds with 2 GB (1 GB read + 1 GB write)?

No, it was only one-way copy. And I did not do a calculation error as the 'Speed' option of Enhancer-Copy gives practically the same result ;). It is also strange that I get somewhat higher speed with the default 128K buffer:

3.Linux-NTFS:> copy-en Test.mp4 ram:  speed
SPEED option 
being quiet during copy...

Copied 963.61 MB in 11.411 seconds at 84.44 MB/s
Copy buffer size
128 KB
Version
54.5

I begin to suspect this is somehow related to the memory management of X5040... I have to wait a few weeks before I have an opportunity to test this with a X5020. But I hope geennam can soon tell what kind of results he gets with a NTFS partition.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@geennaamQuote:
This command will make the shell print the execution speed of a shell command:

prompt "%N.%S [%E s] >"

Thanks for the tip! Very handy feature...

I tested both AOS4 and Enhancer Copy (16MB buffer, 1 GB, file, NVMe NTFS->RAM):

74,35 MB/s (AOS4)
75.93 MB/s (Enhancer)

So, the Enhancer Copy seems to be only slightly faster.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@joergQuote:
I don't understand why Hitachi SATA is faster than OWC SATA on AmigaOS, but it's the other way round on Linux.
The absolute results will of course always be different between AmigaOS and Linux, but the relative differences shouldn't be.

Can the basic formating affect anyhow SCSISpeed? OWC and Hitachi has both RDB (I think Hitachi has been formatted with MorhOS), but Kingston has GPT (I wish I remembered the right combination ;) as it is used primarily for Linux.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@joergQuote:
To compare the Linux results from the Hyperion forum you'd have to use something like
SCSISpeed nvme.device:0 LONG FAST BUF1 10485760 BUF2 104857600 BUF3 1073741824 BUF4 1073741824

I got this kind of results with SCSISpeed in X5040:

Buffer             Kingston         OWC              Hitachi
******             *********         *****              *******
10 MB              53.3              25.7               60.5
100 MB            60.8              30.2               61.9
1 GB                97.5              46.5               60.2     
(MB/s)

KingstonNV2 NVMe 500GB (Axagon PCIe x4 adapter)
OWCMercury Electra 3G SSD 120GB (onboard Sata2 controller)
Hitachi mechanical Sata HD 160GB (onboard Sata2 controller)

When I run at Linux side the 'whole disk' test with 'Disks' tool, it gave in average for Kingston 990 MB/s, OWC 180 MB/s and Hitachi 50 MB/s read speeds (the sample sizes were the same as buffers above),

It surprices me how well the old mechanical Hitachi performed with SCSISpeed, compared to the SSDs. In real life it is dog-slow, if used e.g. for loading Linux programs!

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@geennaamQuote:
No I use the OS4 copy command. And I do not use a SPEED option but the BUF option.

But how do you measure the transfer time...? At least the v. 53.6 Copy does not show it.

Quote:
Can I create and format a Fat or Ntfs partition with aos4? Or do have to do so on another OS?

Yes, you can do it with AOS4. In Mediatoolbox choose the 'type:' "Custom file system" and then input the 'identifier:' " 0x4E544653" (NTFS) or "0x4D534400" (FAT). Also exFAT ("0x45584641") should be available but have not tested it.

After rebooting the partitions should be visible on WB and can be formated.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@joergQuote:
You are using 10MB/100MB/1GB reads on Linux and compare them with 128KB ones (which are additionally twice as slow since you don't just use reads but copies from/to RAM: instead) on AmigaOS? Seriously?

I think you are now too severe towards an old man... I am not a professional computer expert nor a programmer. I thought the 1 GB filesize used by geenam would be comparable to the sample size used in 'Disks' tool, not the buffer size. Forgive my ignorance...

Quote:
To compare the Linux results from the Hyperion forum you'd have to use something like
SCSISpeed nvme.device:0 LONG FAST BUF1 10485760 BUF2 104857600 BUF3 1073741824 BUF4 1073741824
instead.

Thanks! It is always best to give a simple and clear recipe how to do things right, instead of blaming. I will try that later...

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@joergQuote:
geennaam is using 16 MB, but I don't know if he is using the AmigaOS or the Enhancer C:Copy.

I tested now with 16MB buffer but got actually lower speed (75 MB/s) than with 128K (84 MB/s).

AmigaOS Copy does not have the 'SPEED' option.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@geennaamQuote:
The filesystem itself. Apparently the Amiga implementation is slow. Do you manage 1GB on the X5000 with Linux? Or on a Pc?

Naturally on the X5000 . Please see details here:
https://forum.hyperion-entertainment.c ... wtopic.php?p=56906#p56906

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@daveywQuote:
Interesting. AEON have built a replacement Copy command in the Enhancer pack, do you know if it incorporates what you have suggested?

As said, it was exactly that enhancer version I used for testing, and I think also @geennaam used it as the original 'Copy' does not have the 'SPEED' option.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@joergQuote:
Using C:Copy from/to RAM: for benchmarks doesn't make any sense, and it's not comparable at all if you don't even include the BUF size you used in the results (the default is way too small).
Even using DiskSpeed is much better than that.

I was simply using the same method as @geennaam to get results comparable to his ones, nothing more. Those values I gave are for the default buffer size (128K), but did not get significantly better results with e.g. 512K or 1024K. How large SHOULD the buffer be to work optimally with a 1GB file?

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@geennaamQuote:
No I haven't. But as you can read above. The driver itself manages well beyond 1GigaByte/s. The limitation is in the filesystem.

Do you mean the filesystem itself, or how well AmigaOS can handle that filesystem? In Linux I can get over 1GB/s speed with the very same NTFS partition, so the limitation seems to be only on the Amiga side.

Go to top


Re: NVMe device driver
Just popping in
Just popping in


@geennaam

Have you already tested the speed of NTFS and FAT partitions with your driver? When I tested NTFS (using the copy command from enhancer package and a 1GB file), I got 84 MB/s for NVMe->RAM and 66 MB/s for RAM->NVMe. Much slower than I expected...

Go to top


Re: First user's report of new Intel HD Audio (Azalia) driver by geennaam
Just popping in
Just popping in


@geennaam

>I see reports that it is working with x86 linux distros. Some users with problems simply
>forgot to unmute the card. Never tried linux on ppc so I'm not sure how mature that is.
>
>But the audigy FX is nothing special. So there should be no reason why it shouldn't work.

As I suspected from the beginning, Audigy FX does NOT work with Amiga Linux:

https://forum.hyperion-entertainment.com/viewtopic.php?f=58&t=4703

So, unfortunately it is an 'AmigaOS-only' soundcard . The old Sound Blaster Live! is probably still the the best choise for multiOS AmigaONEs, if you just happen to find one.

Go to top


Re: First user's report of new Intel HD Audio (Azalia) driver by geennaam
Just popping in
Just popping in


@geennaam

In this thread there were more complicated problems than just having forgotten to unmute the card:

https://www.linuxquestions.org/questio ... gy-fx-to-work-4175505881/

Go to top


Re: First user's report of new Intel HD Audio (Azalia) driver by geennaam
Just popping in
Just popping in


@geennaam

>If Radeon hdmi audio works for you under linux (X5000) then this card
>should work too. They are both HD audio and use the same linux driver.

Yes, hdmi audio works, but at least earlier many intel Linux users have reported problems to get that card really working instead of the hdmi one. I do not know what is the situation with latest kernels... So, I hope someone using X5000 and the Audigy card can confirm this!

BTW, would it be possible to use the hdmi audio also with your driver, under AmigaOS?

Go to top


Re: First user's report of new Intel HD Audio (Azalia) driver by geennaam
Just popping in
Just popping in


@kas1e @all

Does the Sound Blaster Audigy FX work also with Linux (in X5000)? Not any recognition problems caused by the onboard audio chip of Radeon graphics cards...?

Go to top



TopTop
« 1 (2)




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project