Hic-ups every 30 secs

[capone]

I understand now. So this is acting all the time, really? Chekcing to see if needs to act recording set or secheduled? I can also see where is this is a must-do function, then.

I wonder if the check was against something aside from an MDB file, if it would do the same. As in, what if all recordings were kept in an XML file as well, and that was the file checked? As a different file type, it may act more passivly.

[sub]

I wonder if the check was against something aside from an MDB file, if it would do the same. As in, what if all recordings were kept in an XML file as well, and that was the file checked? As a different file type, it may act more passivly.

To be honest, I dont think its even to do with checking the file. Getting the date time on a file is a pretty much instant activity, with very minimal overheads.

[capone]

To be honest, I dont think its even to do with checking the file. Getting the date time on a file is a pretty much instant activity, with very minimal overheads.

But the problem exists, nonetheless. It's happening in concert w/ those checks, so no matter how illogicial and unlikely, it's still the most obvious and likely cause.

There's an old web designer joke:
Q: How many web deisgners does it take to change a light bulb?
A: The light is working just fine here, it must be your bulb.

My whole day is fixing programing problems I'm not having, so I know what this is like (which is also part of why I got interested). The point of my joke was that sometimes you need to try to fix what can't logically be the problem, because somehow it is anyway.

I know you're going to add something that will be an optional setting to help folks, but at some cost it sounds. I'm just suggesting not ruling out fixes that, on the surface, should not help, but may do so w/o trashing something else.

You may also find a way to optimize the whole thing along the way. I almost always gain some new code when I get clever fixing a problem and not patching it.

Just some thoughts. Again, I know this situtation all to well, so just empathizing, and supporting the supporter here.

[sub]

To be honest, I dont think its even to do with checking the file. Getting the date time on a file is a pretty much instant activity, with very minimal overheads.

But the problem exists, nonetheless. It's happening in concert w/ those checks, so no matter how illogicial and unlikely, it's still the most obvious and likely cause.

No, its not the most likely cause - jsteele and a couple of others have had this problem prior to adding the file date/time check in. The file date/time check was an attempt at fixing the problem.

I'm guessing its to do with the .net remoting call that happens when the client calls the server.

I know you're going to add something that will be an optional setting to help folks, but at some cost it sounds

The setting I'm putting in wont help anyone, but it'll also not harm anyone. It'll be an optional setting, off by default. It'll only add an additional diagnostic avenue for us. I suspect we'll only turn on for a couple of people once or twice to see what happens, then rest of the time (and for everyone else) it'll be exactly the same as now.

[capone]

No, its not the most likely cause - jsteele and a couple of others have had this problem prior to adding the file date/time check in. The file date/time check was an attempt at fixing the problem.

I'm guessing its to do with the .net remoting call that happens when the client calls the server.

I didn't mean cause as in you made the probem kind of thing. I was just saying you have something happening every 30 sec that windows is not handling properly (eg, the majorty of us).

Sounds like you'll have a fix for these folks soon enough, anyway, so I'll step out. I was just trying to offer some diagnostic idea. Like I said, I know what it's like trying to fix a problem you don't even have.

[Kyle]

These file accesses happen every 30 seconds corresponding with the hiccup. I was only able to post part of the information due to the 10000 character limit in this forum. There are a combined total of 170 file accesses to the gbpvr.mdb and gbpvr.ldb every 30 seconds which exactly corresponds to the hiccup. The process name was truncated but you can see that it is obviously the GBPVRRecordingService.

This "burst" of database access and cpu spike happens for me while time shifting and also while watching while recording. If I am recording without watching or just watching Live TV then there is no burst of database access and also no cpu spike.

I'd be willing to believe that 170 file accesses to 2 different files including reading, writing, locking, and unlocking in ~1 second time period could cause a hiccup. Anybody besides me think it's a little suspicious that this burst of database access seems to correspond and happen under the same conditions as the cpu spike ?

Kyle

2325 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Attributes: A
2326 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Attributes: A
2337 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Attributes: A
2345 2:19:02 PM GBPVRRecordingS:3248 OPEN C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Options: Open Access: All
2346 2:19:02 PM GBPVRRecordingS:3248 OPEN C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Options: Open Access: All
2347 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS FileFsVolumeInformation
2348 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS FileInternalInformation
2349 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Length: 2830336
2350 2:19:02 PM GBPVRRecordingS:3248 CLOSE C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS
2351 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS FileFsVolumeInformation
2352 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb BUFFER OVERFLOW FileAllInformation
2353 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Length: 2830336
2354 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Length: 2830336
2355 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 0 Length: 65536
2356 2:19:02 PM GBPVRRecordingS:3248 OPEN C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Options: OpenIf Access: All
2357 2:19:02 PM GBPVRRecordingS:3248 OPEN C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Options: Open Access: All
2358 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS FileFsVolumeInformation
2359 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS FileInternalInformation
2360 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Length: 320
2361 2:19:02 PM GBPVRRecordingS:3248 CLOSE C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS
2362 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS FileFsVolumeInformation
2363 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb BUFFER OVERFLOW FileAllInformation
2364 2:19:02 PM GBPVRRecordingS:3248 CLOSE C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS
2365 2:19:02 PM GBPVRRecordingS:3248 OPEN C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Options: Open Access: All
2366 2:19:02 PM GBPVRRecordingS:3248 OPEN C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Options: Open Access: All
2367 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS FileFsVolumeInformation
2368 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS FileInternalInformation
2369 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Length: 320
2370 2:19:02 PM GBPVRRecordingS:3248 CLOSE C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS
2371 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS FileFsVolumeInformation
2372 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.ldb BUFFER OVERFLOW FileAllInformation
2373 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435457 Length: 255
2374 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435712 Length: 255
2375 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435712 Length: 1
2376 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435457 Length: 1
2377 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435713 Length: 1
2378 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435458 Length: 1
2379 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435714 Length: 1
2380 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb NOT GRANTED Excl: Yes Offset: 268435459 Length: 1
2381 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 268435715 Length: 1
2382 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 268435460 Length: 1
2383 2:19:02 PM GBPVRRecordingS:3248 WRITE C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Offset: 192 Length: 64
2384 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 268436736 Length: 256
2385 2:19:02 PM GBPVRRecordingS:3248 UNLOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Offset: 268436736 Length: 256
2386 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 2764800 Length: 4096
2387 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 2772992 Length: 4096
2388 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Length: 2830336
2389 2:19:02 PM GBPVRRecordingS:3248 QUERY INFORMATION C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Length: 2830336
2390 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 1073753092 Length: 1
2391 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 90112 Length: 4096
2392 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 94208 Length: 4096
2393 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 98304 Length: 4096
2394 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 1073777668 Length: 1
2395 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 286720 Length: 4096
2396 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 290816 Length: 4096
2397 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 294912 Length: 4096
2398 2:19:02 PM GBPVRRecordingS:3248 UNLOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Offset: 1073777668 Length: 1
2399 2:19:02 PM GBPVRRecordingS:3248 UNLOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Offset: 1073753092 Length: 1
2400 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 1073753092 Length: 1
2401 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 90112 Length: 4096
2402 2:19:02 PM GBPVRRecordingS:3248 LOCK C:\Program Files\devnz\gbpvr\gbpvr.ldb SUCCESS Excl: Yes Offset: 1073777668 Length: 1
2403 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 286720 Length: 4096
2404 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 299008 Length: 4096
2405 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 303104 Length: 4096
2406 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 307200 Length: 4096
2407 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 102400 Length: 4096
2408 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 311296 Length: 4096
2409 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 315392 Length: 4096
2410 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 319488 Length: 4096
2411 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 323584 Length: 4096
2412 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 360448 Length: 32768
2413 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 327680 Length: 4096
2414 2:19:02 PM GBPVRRecordingS:3248 READ C:\Program Files\devnz\gbpvr\gbpvr.mdb SUCCESS Offset: 331776 Length: 4096

[ram4x4nut]

Bump, just so sub will be sure to see the errors posted.

[daza67]

I also experienced this 30 sec problem last night. Was getting a major stutter coinciding with a 100% peak in cpu usage exactly every 30 seconds. I pinned it down to the lcdsmartie plugin http://forums.nextpvr.com/showthread.php?t=7067 which I'd reinstalled that day.

This plugin is used in conjuntion with the myvideos plugin however using that plugin alone did not seem to cause the issue.

[daza67]

I'll also add my setup is almost identical to fiteclub's.

[stefan]

I also experienced this 30 sec problem last night. Was getting a major stutter coinciding with a 100% peak in cpu usage exactly every 30 seconds. I pinned it down to the lcdsmartie plugin http://forums.nextpvr.com/showthread.php?t=7067 which I'd reinstalled that day.

This plugin is used in conjuntion with the myvideos plugin however using that plugin alone did not seem to cause the issue.

Doesn't sound like something many of us use...