Is there any documentation available about what block size MEMDISK uses to load (big iso/harddisk) image files? Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted in the following, depending on specified block size: * 2048 bytes --> 25MB/s * 2MB --> 61MB/s It would be nice to know at which speed MEMDISK is loading, but a stopwatch seems a bit crude as only method. Bernd
On 09/21/2012 02:02 PM, Bernd Blaauw wrote:> Is there any documentation available about what block size MEMDISK uses > to load (big iso/harddisk) image files? > > Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s > read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted > in the following, depending on specified block size: > * 2048 bytes --> 25MB/s > * 2MB --> 61MB/s > > It would be nice to know at which speed MEMDISK is loading, but a > stopwatch seems a bit crude as only method.MEMDISK doesn't load anything. Syslinux loads things, and uses a block size of (typically) 63.5K which is the maximum supported by EDD 3.0. -hpa
On 09/21/2012 02:02 PM, Bernd Blaauw wrote:> Is there any documentation available about what block size MEMDISK uses > to load (big iso/harddisk) image files? > > Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s > read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted > in the following, depending on specified block size: > * 2048 bytes --> 25MB/s > * 2MB --> 61MB/s > > It would be nice to know at which speed MEMDISK is loading, but a > stopwatch seems a bit crude as only method. >Note: cptime.c32 would have exactly the same limitation, so your "2MB" there is really 63.5K. -hpa