misi01 Advanced
Joined: 02 Dec 2002 Posts: 629 Topics: 176 Location: Stockholm, Sweden
|
Posted: Thu Aug 12, 2010 7:31 am Post subject: |
|
|
Another possible thought is the following. Since you assume that the date calculation is what's hogging CPU, why not try something along these lines.
Create a copy of the existing program calling it something else. Instead of doing any date calculations, simply "pretend" that the date calculation for record 1 results in process 1 and do it. Record 2 performs process 2, 3 process 3 etc etc (or simply randomise which process is performed for which record).
Now run the existing code and the new code and compare the CPU time taken - this should give you a good idea as to whether you're attacking the right area for performance |
|