Am 05.08.2013 19:04, schrieb jicman:
so its totaly unclear if the presented code is your 2h monster,
what was
the runtime of your jscript?
The files are in a network drive, so, that has some slowness
already involved because of that. The jscript use to take over 8
hours. The new D program has dropped that to under less than
six. This is huge to us. But, I know that I can probably fine
tune the program to make it a few minutes less. :-)
can you describe more detailed what are you doing - are you also reading
these files? why not run your tool on the server and only collect the
results over network (wouldn't that be much faster)?
what is the impact of using the networkdrive? just copy your biggeste
szenario on a local machine an run it against this to get a feeling how
painfull the networkdrive communication is
> But I see that a great idea has been provided
using a local variable for not lowercasing on each if is not an
great idea it is default programming style
This will help. If there are 100K files, which I know that there
are more than that, it will help a little bit.
and i don't think you're be able to implement the tree
statemachine
when doing such simple performance killer like multiple
lowercase calls, and try to help youselfe by introducing
"continue"...
Perhaps, but it's a good idea, nonetheless.
maybe your program can be better optimized globaly, but we need more
information of what is the programing doing - can you give some
psuedo code like:
1. read all filenames recursivley -> 100k filenames
2. reduce down to known extensions -> 10k filenames
3. ...
4. ...
5. ...
i don't think that your lower-case is the major part of the 6h, there
must be other very slow parts in your project - which you don't find
without putting in some bechmarking (and i don't understand why you
don't start with benchmarking)
