07-29-2013 08:02 AM
Hi,
I have developed a small applications. one is test exe and other is timer.exe.Timer exe calculates the execution time taken for test.exe( checks for test.exe in task manager and displays the execution time). The time taken to execute the test exe is around 2 secs in XP where as in Win7 its taking 4 to 5 seconds. Any ideas on why this is happening or how i could fix the problem?
07-29-2013 08:41 AM
When does your benchmarking start? Is it "synchronized" to a special situation in your "test.exe"?
My guess is that one of the following (or any combination) is hitting you:
- More restrictive firewall
- Anti-virus software scans more intensively
- Restricted user priviliges
- Harddrive is less performant
- Less RAM
- 32bits vs. 64bits (WoW64?)
- Different LV version and/or different compiler options
- Depending on third party software which might induce delays
- Different CPU performance (e.g. for number crunching, CPU/ALU are possibly optimized for specific settings)
- ...
You see, there are too many possible factors for this behavior....
Norbert
07-29-2013 08:53 AM
What kind of task is performed by test.exe?
Marco
07-30-2013 05:36 AM
Test.exe is a small appication which adds two numbers and exits LabVIEW.
07-30-2013 09:05 AM
Might it be that the Win7 is 64 bit? If so, you'll start wow32 (or what it's called) as well as LV runtime. Your simple test program fills little purpose.
/Y
08-02-2013 10:00 AM
Is it polling the task manager a reliable way of measuring the execution time?
Try measuring the execution time inside test.exe (and writing it to a file...).
Is it still so differentì?
Regards,
Marco
08-02-2013 11:46 AM
@swasa wrote:
Hi,
I have developed a small applications. one is test exe and other is timer.exe.Timer exe calculates the execution time taken for test.exe( checks for test.exe in task manager and displays the execution time). The time taken to execute the test exe is around 2 secs in XP where as in Win7 its taking 4 to 5 seconds. Any ideas on why this is happening or how i could fix the problem?
Your test is flawed if you measure from double click icon until finished, or do the program has some timing to measure time? Post the VI.
/Y