Upgraded to Win7, now jerky scrolling

[graywolf]

Installed Win7 and SageTV on new harddrive.
Restored pre-upgrade backup of SageTV directories to newly installed SageTV.

Notice that going thru menu lists (sage recordings, guide, scheduled recordings) that it seems to be jerky.

Sometimes when hitting the down button quickly, it will even pause then "skip" several lines.

Have not noticed the sporadic spinning circles that we had before.

I have upped the JVMMaxHeapSizeMB to 1024

Any thoughts on how you get rid of the "jerkiness"?
Negative impact to WAF

[nyplayer]

Originally Posted by graywolf

Installed Win7 and SageTV on new harddrive.
Restored pre-upgrade backup of SageTV directories to newly installed SageTV.

Notice that going thru menu lists (sage recordings, guide, scheduled recordings) that it seems to be jerky.

Sometimes when hitting the down button quickly, it will even pause then "skip" several lines.

Have not noticed the sporadic spinning circles that we had before.

I have upped the JVMMaxHeapSizeMB to 1024

Any thoughts on how you get rid of the "jerkiness"?
Negative impact to WAF

Is this on the upgraded box or clients if it is on the upgraded box maybe your video card is just meeting the minimum requirements for win 7 and does not handle hardware acceleration very well in win 7.

[graywolf]

Using HD-200 & HD-300

So I wouldn't think the Graphics card on the server would matter.

Any other settings that might need to be adjusted going from XP to WIN7?

Only other change to hardware was adding another 4GB RAM (was 2GB, now 6GB)

[nyplayer]

Originally Posted by graywolf

Using HD-200 & HD-300

So I wouldn't think the Graphics card on the server would matter.

Any other settings that might need to be adjusted going from XP to WIN7?

Only other change to hardware was adding another 4GB RAM (was 2GB, now 6GB)

I have Autotuning Disabled.

Disable Windows Scaling heuristics
Windows Vista/7 has the ability to automatically change its own TCP Window auto-tuning behavior to a more conservative state regardless of any user settings. It is possible for Windows to override the autotuninlevel even after an user sets their custom TCP auto-tuning level. When that behavior occurs, the "netsh int tcp show global" command displays the following message:
** The above autotuninglevel setting is the result of Windows Scaling heuristics
overriding any local/policy configuration on at least one profile.
To prevent that behavior and enforce any user-set TCP Window auto-tunning level, you should execute the following command:
netsh int tcp set heuristics disabled
possible settings are: disabled,enabled,default (sets to the Windows default state)
recommended: disabled (to retain user-set auto-tuning level)
Note this should be executed in elevated command prompt (with admin priviledges) before setting the autotuninlevel in next section. If the command is accepted by the OS you will see an "Ok." on a new line.

TCP Auto-Tuning
To turn off the default RWIN auto tuning behavior, (in elevated command prompt) type:
netsh int tcp set global autotuninglevel=disabled
The default auto-tuning level is "normal", and the possible settings for the above command are:
disabled: uses a fixed value for the tcp receive window. Limits it to 64KB (limited at 65535).
highlyrestricted: allows the receive window to grow beyond its default value, very conservatively
restricted: somewhat restricted growth of the tcp receive window beyond its default value
normal: default value, allows the receive window to grow to accommodate most conditions
experimental: allows the receive window to grow to accommodate extreme scenarios (not recommended, it can degrade performance in common scenarios, only intended for research purposes. It enables RWIN values of over 16 MB)

[graywolf]

Thanks. I'll give this a try and see if it helps with the WAF

[graywolf]

Still no good.

HD-200/HD-300

When hitting the down (or up) button on the remote rapidly while going thru a list, it sometimes pauses then jumps/skips to catch up.

This has caused the wife to mis-hit/select a couple times to include deleting show accidentally (was able to recover from "recyclebin" on the NAS.

Maybe this isn't a SageTV issue but rather a network issue?

Would a clean install of Win7 have network settings that could be causing this "sputtering/jerkiness"?

[wubdich]

Might be a good idea to check network performance with NetIO (or a similar tool).
- Start NetIO on SageTV Server
- Plug network cable from HD200 to Laptop (with NetIO)
and run some tests.

[mistergq]

Is this the same server with just a new hard drive? What type of hard drive?

Have you switched out the ethernet cable to your router/switch from you server?

This is starting to sound like a hardware failure somewhere.

[graywolf]

It has shown up on both servers that I have "upgraded" from XP to Win7 (both with "new" Hitachi 2TB drives)

Hard Drives were "tested/excersided" before being used (unRaid pre-clear 5 times) and smartmon looked good on them.

I have made "network tweaks" on one of them and I think it has improved it as far as I can tell. Test will be if WAF agrees with me.

No change to cables/routers/switches.

[trk2]

This behavior can be caused by waiting for a sleeping hard drive to spin up.