Welcome, Guest. Please login or register.

Author Topic: Anyone working on PFS3 ??  (Read 18256 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline SHADESTopic starter

  • Sr. Member
  • ****
  • Join Date: Apr 2002
  • Posts: 355
  • Country: au
    • Show all replies
Anyone working on PFS3 ??
« on: June 10, 2011, 11:21:07 AM »
Just wondering if anyone is working on PFS3 to enable big TB partitions for big fast drives etc.....
Just such a shame if it has now been released and no one is interested. Such a great FS.
It's not the question, that is the problem, it is the problem, that is the question.
 

Offline SHADESTopic starter

  • Sr. Member
  • ****
  • Join Date: Apr 2002
  • Posts: 355
  • Country: au
    • Show all replies
Re: Anyone working on PFS3 ??
« Reply #1 on: June 12, 2011, 05:02:15 PM »
Quote from: Piru;644221
Currently almost all changes are generic. Of course the OS3 version is directly benefiting from the changes being made. There's only one SVN tree that has everything. Assuming the file system is ported to AROS and OS4 it'd be highly desirable to have those changes in the same SVN as well.

Anyone wishing to contribute should contact mr Pelt over sourceforge.


Very glad to to see porogress Piru.Tell michael to fix the donate button on the page.
It's not the question, that is the problem, it is the problem, that is the question.
 

Offline SHADESTopic starter

  • Sr. Member
  • ****
  • Join Date: Apr 2002
  • Posts: 355
  • Country: au
    • Show all replies
Re: Anyone working on PFS3 ??
« Reply #2 on: June 12, 2011, 05:44:49 PM »
Quote from: itix;644025
SFS stops being fast when admin blocks are cluttered over the disk. Performance degrades faster if you are using .recycled directory but reality is that newly formatted SFS disk is always faster than old empty SFS disk.


Just for interest sake.

Some performance stats testing I did on newly created, freshly formatted partitions on my A4000 FastlaneZ3 SCSI equipped PC.

SFS should be at its fastest this way. PFS still kills SFS in speed.

PFS3020ds

MKSoft DiskSpeed 4.2 Copyright © 1989-92 MKSoft Development
------------------------------------------------------------
CPU: 68030 AmigaOS Version: 45.57 Normal Video DMA
Device: hd2: Buffers: 250
Comments: DiskSpeed 4.2

CPU Speed Rating: 1521

Testing directory manipulation speed.
File Create: 61 files/sec | CPU Available: 8%
File Open: 147 files/sec | CPU Available: 1%
Directory Scan: 1023 files/sec | CPU Available: 0%
File Delete: 149 files/sec | CPU Available: 9%

Seek/Read: 507 seeks/sec | CPU Available: 0%

PFS3020ds (With Increased buffers)

MKSoft DiskSpeed 4.2 Copyright © 1989-92 MKSoft Development
------------------------------------------------------------
CPU: 68030 AmigaOS Version: 45.57 Normal Video DMA
Device: hd0: Buffers: 512
Comments: DiskSpeed 4.2

CPU Speed Rating: 1522

Testing directory manipulation speed.
File Create: 92 files/sec | CPU Available: 8%
File Open: 146 files/sec | CPU Available: 0%
Directory Scan: 1024 files/sec | CPU Available: 0%
File Delete: 149 files/sec | CPU Available: 7%

Seek/Read: 508 seeks/sec | CPU Available: 0%

SFS/2 (With Increased buffers to 600)

MKSoft DiskSpeed 4.2 Copyright © 1989-92 MKSoft Development
------------------------------------------------------------
CPU: 68030 AmigaOS Version: 45.57 Normal Video DMA
Device: hd1: Buffers: 600
Comments: DiskSpeed 4.2

CPU Speed Rating: 1521

Testing directory manipulation speed.
File Create: 61 files/sec | CPU Available: 3%
File Open: 133 files/sec | CPU Available: 2%
Directory Scan: 668 files/sec | CPU Available: 0%
File Delete: 21 files/sec | CPU Available: 2%

Seek/Read: 78 seeks/sec | CPU Available: 0%

SFS/2 (Only 100 buffers)
MKSoft DiskSpeed 4.2 Copyright © 1989-92 MKSoft Development
------------------------------------------------------------
CPU: 68030 AmigaOS Version: 45.57 Normal Video DMA
Device: hd1: Buffers: 100
Comments: DiskSpeed 4.2

CPU Speed Rating: 1520

Testing directory manipulation speed.
File Create: 56 files/sec | CPU Available: 3%
File Open: 132 files/sec | CPU Available: 0%
Directory Scan: 668 files/sec | CPU Available: 0%
File Delete: 44 files/sec | CPU Available: 10%

Seek/Read: 77 seeks/sec | CPU Available: 0%
It's not the question, that is the problem, it is the problem, that is the question.