Enhanced Web Admin

[jsteele]

Interestingly it is only on the login. Although there is significant CPU activity retrieving the guide pages it is NOT in GBPVRRecordingServices and it does not cause display problems in the video.

I don't see that delaying the guide page loading would have an adverse effect, but I also don't see that it would change the situation --- as I noted the spike only occurs at the initial login.

My system has been set to Autologin. So I just tried another experiment and changed the login from Autologin to require a username. When I then opened the web admin the login page was presented. When I entered the username/password the spike occured at that point, during the actual internal login processing.

[normanr]

hrmmm, when does it happen if you use autologin and try and access the config pages?

[jsteele]

I just tried it. I have autologin set so the initial access to the web server results in the spike. Then accessed Config which requests the login. Entered the login and the spike does NOT occur at this point. I tried this four times to confirm that this behavior is consistent.

Whatever it is it APPEARS isolated to the initial login processing.

[normanr]

Okay, so the spike in not caused by the login page, good. Does the spike occur each time you open a new browser or it is happening each time you restart the recording service?

(p.s. thanks for hanging in there on debugging this one!)

[jsteele]

Yes, it appears the the spike occurs only during the INITIAL login when a fresh browser session has opened. AS I reported, once the browser is accessing, the subsequent login for the Config page does not cause the spike. As near as I can tell it only happens on a new browser access and it EVERY time a new browser session opens against the web server.

Although in the past I have tried stopping/restarting GBPVRRecordingService in the past at the time I was not looking for a correlation with anything else. Now it seems to be clearly, reproducibly, related to the web server initial login.

[normanr]

if you close the browser, and open a fresh one (without restarting the service) does it spike?

[jsteele]

Yep, every time

[normanr]

hmm, okay so it's unlikely to be when the web server starts up, and gets the first request, but more when a new browser session is detected...... yegh. I'll do some looking here, but I'm not sure if there's much that can be tweaked.

[jsteele]

normar

Just FYI, I just upgraded to the new release and the problem still occurs in this release.

John

[normanr]

yea, no surprise. It's going to be a .net framework issue, I bet.