Delay in logging and response after upleveling from 7.5 to 9.2

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Upleveled from Artisan 7.5 to 9.2
2.The next 2 batches noted a 10 to 15 second lag in roast logging vs batches 
previous day batches using 7.5
3. Roaster 10 KG Samiac

What is the expected output? What do you see instead?

Output as expected, but interaction with buttons and logging lagged noticeably. 
e.g. the logging was 10-15 seconds behind the clock, the program was much 
slower to react to FC Start button press, slow to react to charge etc.

The program was the only application running on an I7 processor. CPU  and 
memory usage verified to be low

What version of the product are you using? On what operating system?

9.2 on WIN8

Please provide any additional information below.

Thanks for the wonderful work you have done! 
I love the program. 
I was going to start playing with Modbus TCP but may have to rollback to 7.5 if 
I can't figure out what is happening. We initially had similar performance 
issues when we tried to run Artisan on an I3 laptop. Migrating to an I7 
computer resolved them. 

A possible factor, Windows installed several updates after I upleveled Artisan 
and in between the roasting sessions. I did verify all were successfully 
installed and none were pending. The computer was rebooted.

If you have any questions please contact me at chaswerner@gmail.com or 
317-525-0525

thanks again,
charlie
Charles Werner

Original issue reported on code.google.com by chaswer...@gmail.com on 17 Feb 2015 at 2:01

[GoogleCodeExporter]

To me this does not look as an implementation issue so I'll close it.

v0.9.2 runs fine for several users under Win8. Actually, this version should be 
faster then any 0.7.x version as the screen update speed was considerable 
improved by applying tricky caching especially for Windows.

I assume that your issue is due to some background indexing done by the 
operating system after updating system components. It might also be caused by 
low memory conditions. Artisan takes quite some memory due to its underpinnings 
and because it is not optimized in that respect.

So my advice is keep the machine running for a while to let the indexing being 
done. Check and increase the hardware memory of the machine if needed. 
Configure a larger sampling interval in Artisan 3-5sec.

Original comment by luther.m...@gmail.com on 19 Feb 2015 at 10:19

• Changed state: Invalid

[GoogleCodeExporter]

Hi,

The problems went away when I rolled back to the 0.7.5 version.

In 0.9.2 we experienced a significant disparity between the elapsed time
displayed by Artisan and a stopwatch. I can email an alog file if you are
interested. There was a time disparity of about 16 seconds immediately at
charge and throughout the roast. It was also slow responding to mouse
clicks for events like first crack.

We never experienced this in in 0.7.5 before or after the issue in 0.9.2

The settings were identical in both versions

We really enjoy sing Artisan. We currently use it for logging, but intend
to migrate to a control capacity in the near future when we transition from
Watlow to Fuji controllers.

Original comment by chaswer...@gmail.com on 1 Mar 2015 at 3:32