Virtual memory, a curious phenomenon

[ivan]

What camera do you have?  I do not remove the cards from my Nikon D60 or D3200 cameras, just plug in the correct USB cable and use  Cameraderie v1.5.3   (C) Copyright 2006, 2007  R L Walsh to copy the photos to my hard disk - very quick, simple and easy to do.

[Remy]

Sorry Dave, this is in mistake. Keep in mind that I do not have a manual, and I do evidence and error, and sometimes I take bad conclusions that then correct.

The correct is:
IFS=C:\OS2\HPFS.IFS /CACHE:2000 /CRECL:4 /AUTOCHECK:GL*
IFS=C:\OS2\FAT32.IFS /cache:2000 /h /q /ac:* /largefiles
rem CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:5000 /S

swappath=L:\ 2000 409600

REM DISKCACHE=D,LW
DISKCACHE=4096000,LW

Provisted screen in Memory ON (I don't know if it will be necessary or not.)

I just did a test changing the 2 lines as Roberto did (cache at 2000 and rem the call).
What I can say is Whouah ! how fast it is on fat32 !  (My HDD on SATA is very fast compared to before where it took long seconds copy a few megabytes.

[Dave Yeo]

Did you try simply turning off lazywrite? The manual is in x:\sys\book where X: is your boot drive. As mentioned, cachef32 does the unicode conversion.

[roberto]

Did you try simply turning off lazywrite? The manual is in x:\sys\book where X: is your boot drive. As mentioned, cachef32 does the unicode conversion.

I have already tried it with the /L: OFF, and copying from the PC to the USB Stick is 3 seconds faster.
But copying from the USB Stick to the PC is 61 minutes, against 7 to 12 minutes.
That difference is a long time.
saludos

[Remy]

Did you try simply turning off lazywrite? The manual is in x:\sys\book where X: is your boot drive. As mentioned, cachef32 does the unicode conversion.

I have already tried it with the /L: OFF, and copying from the PC to the USB Stick is 3 seconds faster.
But copying from the USB Stick to the PC is 61 minutes, against 7 to 12 minutes.
That difference is a long time.
saludos

Hi Roberto,

On  your IFS, use a multiple of 64K for the cache value instead of 4k
|  IFS=C:\OS2\FAT32.IFS /cache:2000 /h /q /ac:* /largefiles                                      << 2000 not good
|  rem CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:5000 /S

As multiple of 64k, use 1984 instead of 2000 and rem out the Call= which will not trap.
IFS=C:\OS2\FAT32.IFS /cache:1984 /h /q /ac:* /largefiles
CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:5000 /S

[roberto]

Hi Remy
I have tried it and slows me 65 minutes, copying from USB stick to HD
saludos

[Remy]

It only use of the next CALL statement.

I had dounbt about my previous tests due I had several processes running in background...
Now, I redo several test in read and write from/to SSD sata partitions (one into fat32, the other as jfs)

I used a very big file and stopped the process after 60s (may be 1/4s differences but as precise as possible)

After 60s (CTRL C) from SATA SSD (fat32) to SATA SSD (JFS)
With -> IFS=C:\OS2\FAT32.IFS /cache:1984 /h /q /ac:* /largefiles
With -> REM CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:ON
15/02/23 23:55    369 011 200      0 a---  dsd64-2ch (3).zip

With -> IFS=C:\OS2\FAT32.IFS /cache:1984 /h /q /ac:* /largefiles
With -> CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:OFF
16/02/23  0:03    567 854 592      0 a---  dsd64-2ch (3).zip

With -> IFS=C:\OS2\FAT32.IFS /cache:2048 /h /q /ac:* /largefiles
With -> CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:OFF
16/02/23  0:13    566 098 944      0 a---  dsd64-2ch (3).zip

With -> IFS=C:\OS2\FAT32.IFS /cache:2048 /h /q /ac:* /largefiles
With -> CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:ON
16/02/23  0:19    566 619 136      0 a---  dsd64-2ch (3).zip

With -> IFS=C:\OS2\FAT32.IFS /cache:2000 /h /q /ac:* /largefiles
With -> REM CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:ON
16/02/23  0:26    370 636 800      0 a---  dsd64-2ch (3).zip


After 60s (CTRL C) from SATA SSD (JFS) to SATA SSD (FAT32)
With -> IFS=C:\OS2\FAT32.IFS /cache:2000 /h /q /ac:* /largefiles
With -> REM CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:ON
16/02/23  0:36    478 121 472      0 a---  dsd64-2ch (3).zip

After 60s (CTRL C) from SATA SSD (JFS) to SATA SSD (FAT32)
With -> IFS=C:\OS2\FAT32.IFS /cache:2048 /h /q /ac:* /largefiles
With -> CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:OFF
16/02/23  0:43    426 882 560      0 a---  dsd64-2ch (3).zip

After 60s (CTRL C) from SATA SSD (JFS) to SATA SSD (FAT32)
With -> IFS=C:\OS2\FAT32.IFS /cache:2048 /h /q /ac:* /largefiles
With -> CALL=C:\OS2\CACHEF32.EXE /f /p:2 /m:50000 /b:250 /d:4000 /S /L:ON
16/02/23  0:50    282 464 256      0 a---  dsd64-2ch (3).zip

In this kind of test, the L:OFF has a big impact but overall, the speed is very very slow for SSD's !
testing from JFS to JFS for one very big file results into nearly 98MB/s which is of course slow for an SSD able to speed up to 520M !
(Disk aligment may probably impact - isn't correctly done for SSD and may be trim need [not done since a few weeks])

I didn't test usb keys yest and I know it needs more time because as soon it warms up, speed will dramatically slowdown
I have a 1TB usb key with a speed nearly 500MB. Under windows, It will start nearly at this speed but after a few seconds, the speed start to drop up to a slow value about 6M ! (the key been warm and into speed regulation to protect it)   
     

[roberto]

I used a very big file and stopped the process after 60s (may be 1/4s differences but as precise as possible)

How do you do the copy and cut it in a time? I have tried it with a zip, and when I cut it I have not copied only one part of the file.

After 60s (CTRL C) from SATA SSD (fat32) to SATA SSD (JFS)

Your test is more fast fat32 to jfs

After 60s (CTRL C) from SATA SSD (JFS) to SATA SSD (FAT32)

Your test is more slow jfs to fat32
With me with the USB stick, it happens to me, it is slower fat32 to jfs.
I am curious to do some proof as you comment.
Saludos

[Remy]

I used a very big file and stopped the process after 60s (may be 1/4s differences but as precise as possible)

How do you do the copy and cut it in a time? I have tried it with a zip, and when I cut it I have not copied only one part of the file.

After 60s (CTRL C) from SATA SSD (fat32) to SATA SSD (JFS)

Your test is more fast fat32 to jfs

After 60s (CTRL C) from SATA SSD (JFS) to SATA SSD (FAT32)

Your test is more slow jfs to fat32
With me with the USB stick, it happens to me, it is slower fat32 to jfs.
I am curious to do some proof as you comment.
Saludos

The zip file has a size near 4GB.
Positionning into the right directory on both side.
Then, from/to issued prompt cmd :  copy filename to w:   or reverse  copy filename to y:
To stop, issued CTRL/C

The problem using a prompt cmd window is that messages are impacted by the video refresh, using one big file prevent copied message to be issued until the end of the copy.

As it is seen, the L:OFF / ON has a big impact on the write (it is for this) on FAT32

Copying files to or from my local network NAS is faster !