Hi Jan, When I said 'string search' I was thinking more along the lines of searching for the filename (the entry into the FAT) and not operations within a string.
It is very interesting that VFSFileOpen on a recently enumerated file is faster. Good observation! Care to share any time measurements? Best regards, Greg Jan Slodicka wrote: > > Hi Greg, > > string operations can't explain anything. They simply cannot take so much > time, however inefficiently written. (Unless it was done with purpose.) > > I found that VFSFileOpen called on just enumerated file is much-much faster > than when it is called after the enumeration terminates. Looks like FAT > search might be that evil. > > Best regards, > Jan Slodicka > > ----- Original Message ----- > From: "Greg Sepesi" <[EMAIL PROTECTED]> > > > > > "On a Zire 31 with all images in one SD directory, the application takes > > 95 seconds to display 400 images. But when the same 400 images are > > partitioned into 8 SD directories, it takes only 53 seconds." > > > > So, the VFSFileOpen was taking about as long as the image drawing. I > > mentioned FAT, but without looking at the source code any attempt at > > explaining the slow performance is of course a blind guess. It may be > > just an inefficient string search (when searching for the specified > > filename). -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
