|
|
Posted by Rob on 01/09/08 14:59
On Jan 9, 12:56 pm, Csaba Gabor <dans...@gmail.com> wrote:
> On Jan 9, 9:34 am, jodleren <sonn...@hot.ee> wrote:
>
> > I have a system, which reads in the entire tree - all files. As of
> > now, there are 1312 folders to read.
>
> > 1st time it takes 53-60 seconds to read. The data is somehow cached,
> > 2nd time time is takes 2-3 seconds.
>
> > Is there a way to "cache" data beforehand? Like "preparing" the
> > directory....?
>
> > WBR
> > Sonnich
>
> You might simply direct the output of the dir
> command into a file (or string or array depending
> on which exec type of command you use) and then
> parse that yourself. It should be FAR faster.
>
> For reference,
> It took my Win XP system about 315 seconds to do:
> C:\>dir /s > delme.dir
> with the entire c: drive, about 140000 files
> totaling about 44 gigabytes in 32000 directories.
> The resultant file was about 10 megabytes
>
> Csaba Gabor from Vienna
If you're running this on Windows, you're probably seeing the Windows
cache coming into play, which is why it runs faster the second time.
As previously suggested, try usign exec() to output a directory to a
file, and then parse that instead.
Rob.
Navigation:
[Reply to this message]
|