Hi All
We have been investigating a speed issue within our VFP application for some time and after testing, we have found the solution to be in a Windows Server 2008 R2.
We can replicate on a 2003 and 2008 SBS server that by rebooting the server, then logging two users into the application working away that after about 20 mins of processing, when one user has a screen open, the other users speed to run a report (in this scenario) goes from 5 seconds to about 1 minute. Once you hit the 20mins, there is no getting the speed back to the 5 seconds unless you reboot the server again.
We have been investigating the SMB route but we have left this to be running at SMB2.
However, as per our customer site and internal, if we use a Windows Server 2008 R2 machine the performance is always good and we never have any problems after the 20minutes.
I know this is strange but has anyone come across this before and is there any knowledge as to why SBS would show this issue. We have number of customers who have resolved this issue by upgrading to R2
Your thoughts would be welcome (scratching my head)
Thanks
We have been investigating a speed issue within our VFP application for some time and after testing, we have found the solution to be in a Windows Server 2008 R2.
We can replicate on a 2003 and 2008 SBS server that by rebooting the server, then logging two users into the application working away that after about 20 mins of processing, when one user has a screen open, the other users speed to run a report (in this scenario) goes from 5 seconds to about 1 minute. Once you hit the 20mins, there is no getting the speed back to the 5 seconds unless you reboot the server again.
We have been investigating the SMB route but we have left this to be running at SMB2.
However, as per our customer site and internal, if we use a Windows Server 2008 R2 machine the performance is always good and we never have any problems after the 20minutes.
I know this is strange but has anyone come across this before and is there any knowledge as to why SBS would show this issue. We have number of customers who have resolved this issue by upgrading to R2
Your thoughts would be welcome (scratching my head)
Thanks