Scheduling_Lookahead in sage.properties file

[paulbeers]

Yes on your server (or just the computer running sage if you don't have a client/server setup) you need to completely shut down everything for sage including the Sage Service. If you don't do this, it will not save. Close all sage applications, update the properties file, and restart Sage.

P.S. I really should do this.

[davidk21770]

Since I have vacation coming up and I want to manually resolve any recording conflicts before we leave, I've upped my scheduling_lookahead=604800000 (7 days, may go more right before we leave).

My question: Is there any penalty for this (other than extra processing to find the shows)? Does it increase the risk of missing any? Say, a lineup change?

Thanks

I asked this in the main forum also, but...

Has anyone who's set the lookahead way up seen any negative impact?
I'm doing it now because I have vacation coming up, but I like seeing that far ahead.

Thanks

[DFranch]

Originally Posted by davidk21770

I asked this in the main forum also, but...

Has anyone who's set the lookahead way up seen any negative impact?
I'm doing it now because I have vacation coming up, but I like seeing that far ahead.

Thanks

No problems here. I've been using it like that for 2 years. I am only using a AMD Athlon 2500+ with 512MB Ram & 3 tuners.

[jptaz]

I had performance problems when I went from 4 Tuners to 6 Tuners....everytime it went to reevaluate the schedule it would peg the CPU at 100% for a minute...now I won't even think about it with 9 Tuners.

John

[ke6guj]

Some people can get away with big lookaheads, but if you have lots of tuners and favorites, you can run into problems like jptaz mentioned.

My system with 5 tuners and 200+ favorites would be ok most of the time, but occasionally would lock up the scheduler if I had a large lookahead. If I added a couple favorites, or let Sage delete a show at the end of a viewing, it would peg the CPU. It eventually got to the point that I had to decrease the lookahead to 2 days (now fixed with newer releases) to run stablely.

IF you only have the 1 tuner shown in your sig, then you would probably be fine. Just test it for a while before you leave with the lookahead you want, don't change it just before you leave like you mentioned.

[DFranch]

Originally Posted by ke6guj

Some people can get away with big lookaheads, but if you have lots of tuners and favorites, you can run into problems like jptaz mentioned.

My system with 5 tuners and 200+ favorites would be ok most of the time, but occasionally would lock up the scheduler if I had a large lookahead. If I added a couple favorites, or let Sage delete a show at the end of a viewing, it would peg the CPU. It eventually got to the point that I had to decrease the lookahead to 2 days (now fixed with newer releases) to run stablely.

IF you only have the 1 tuner shown in your sig, then you would probably be fine. Just test it for a while before you leave with the lookahead you want, don't change it just before you leave like you mentioned.

200+ favorites DAMN! I only have 50 favorites, and I never have any time to watch stuff. You must have 2TB to store all of that.

[Opus4]

The schedule lookahead was throttled quite a while back, so it won't take over the cpu, but it could take quite a while to finish -- it will finish, though you may have to wait longer. (SageTV still isn't going to recommended that the lookahead be set past 3 days.)

There is info about auto-deletion of live tv recoridngs (if that is what you are referring to) starting on p. 236 of the v5 PDF manual, but it looks like there is a glitch in the text toward the end of the section. The property the Detailed Setup option should be referring to at the end is seeker/clear_partials_and_unwanted_when_ir_off.

The default STV can ask to delete existing recordings after you watch it, controlled by a setting in Detailed Setup -> Customize.

- Andy

[ke6guj]

Originally Posted by DFranch

200+ favorites DAMN! I only have 50 favorites, and I never have any time to watch stuff. You must have 2TB to store all of that.

Well, since I work from home, I am in front of a TV a lot . And I only have about 500GB used on a 1.3TB RAID array right now. When the fall season starts, It'll fill up fast. Gotta think about adding more HD's to the RAID

Originally Posted by Opus4

The schedule lookahead was throttled quite a while back, so it won't take over the cpu, but it could take quite a while to finish -- it will finish, though you may have to wait longer. (SageTV still isn't going to recommended that the lookahead be set past 3 days.) .

Yup, A while ago the scheduler got a lot better, not exactly sure when, late V4 IIRC. Since then, I have had no problems with the scheduler pegging the CPU, but I also haven't increased the lookahead to more than 3 days.

[davidk21770]

Originally Posted by ke6guj

Some people can get away with big lookaheads, but if you have lots of tuners and favorites, you can run into problems like jptaz mentioned.

My system with 5 tuners and 200+ favorites would be ok most of the time, but occasionally would lock up the scheduler if I had a large lookahead. If I added a couple favorites, or let Sage delete a show at the end of a viewing, it would peg the CPU. It eventually got to the point that I had to decrease the lookahead to 2 days (now fixed with newer releases) to run stablely.

IF you only have the 1 tuner shown in your sig, then you would probably be fine. Just test it for a while before you leave with the lookahead you want, don't change it just before you leave like you mentioned.

Thanks. I only have one tuner and about 15 favorites, so I should be fine. And, I'm testing this week and next before leaving (Good suggestion!).

[hemicuda]

or is the scheduler only going 12 days ahead w/ the setting at 1209600000. unless the EPG service is only sending out 12 days of data I should see recordings listed from today until tuesday-after-next. right? it's been giving me 12 days for a long time.

[ke6guj]

I only have 12 days of EPG data right now. It seems to fluctuate between 12-14 days most of the time. I'm not sure how often Sage updates the EPG feed, if it is supposed to always have 14 days of upcoming data. If you currently only have 12 days of EPG downloaded, you obviously can't schedule stuff out to 14 days