Sage startup time

[Doubledose]

How long does it normally take sage tv to load up? I am taking about 1 1/2 minutes to load up. I thought it was because I had 2 old tuners that I had disabled. I pulled them out this morning and took all references to the cards out of sage properties file ( see post below ) but still takes forever for sage to load. Is this normal for version 9? I don't remember it taking as long when I was running v7. V9 was an update install.
Thanks for any info
Wayne

[NetworkGuy]

See this post for a possible solution. https://forums.sagetv.com/forums/sho...light=start-up

[Doubledose]

Thanks for the info. That seams to have made a big difference. I looked right by that post, did not put initializing with long boot time.
Thanks
Wayne

[waynedunham]

Originally Posted by Doubledose

How long does it normally take sage tv to load up? I am taking about 1 1/2 minutes to load up. I thought it was because I had 2 old tuners that I had disabled. I pulled them out this morning and took all references to the cards out of sage properties file ( see post below ) but still takes forever for sage to load. Is this normal for version 9? I don't remember it taking as long when I was running v7. V9 was an update install.
Thanks for any info
Wayne

Wow, I wish I could get startup times even remotely close to that! Startup from starting the SageTV service until I can "see" the server on my extenders is over 20 minutes for me on both of my SageTV servers.

I can't use the info in the link given because I DO use Intelligent Recording so I can't really delay that. Probably contributing to the slow startup for me is the # of tuners I have on each server (8 on one and 9 on the other) with multiple lineups on each server as well. (Cable for STB/HD-PVR, Cable limited for HDHR Prime and OTA)

I don't know why, but V9 is even slower than V7 was. Same # of tuners, same lineups yet my startup time has almost doubled.

[egeller]

For me, restarting SageTV has to be a planned event. Before restarting, I go through the schedule of upcoming recordings for the next 12 hours, mark the intelligent recordings I want to record as manual recordings, then restart Sage, using the fast-restart option. Sage comes back quick, recording favorites and manual recordings. However, intelligent recordings are not scheduled for about 7 hours or so. I do not remember it being much different with V7. I recently moved SageTV from Windows 10 to Unraid, and it still takes about the same 7 hours or more.

[stanger89]

Originally Posted by NetworkGuy

See this post for a possible solution. https://forums.sagetv.com/forums/sho...light=start-up

That's the setting you want, if you've got a lot of history, it can take Sage a very long time to initialize without it.

[Tiki]

Originally Posted by waynedunham

Wow, I wish I could get startup times even remotely close to that! Startup from starting the SageTV service until I can "see" the server on my extenders is over 20 minutes for me on both of my SageTV servers.

I can't use the info in the link given because I DO use Intelligent Recording so I can't really delay that. Probably contributing to the slow startup for me is the # of tuners I have on each server (8 on one and 9 on the other) with multiple lineups on each server as well. (Cable for STB/HD-PVR, Cable limited for HDHR Prime and OTA)

I don't know why, but V9 is even slower than V7 was. Same # of tuners, same lineups yet my startup time has almost doubled.

I don't understand the logic here. Changing this property won't disable intelligent recordings, it just delays them a bit. IR is just meant to fill in the gaps and catch some additional shows you might be interested in. Nothing it records should be considered critical (if something you really care about is on, it should be set as a Favorite or Manual Recording).

[EnterNoEscape]

Originally Posted by waynedunham

Wow, I wish I could get startup times even remotely close to that! Startup from starting the SageTV service until I can "see" the server on my extenders is over 20 minutes for me on both of my SageTV servers.

I can't use the info in the link given because I DO use Intelligent Recording so I can't really delay that. Probably contributing to the slow startup for me is the # of tuners I have on each server (8 on one and 9 on the other) with multiple lineups on each server as well. (Cable for STB/HD-PVR, Cable limited for HDHR Prime and OTA)

I don't know why, but V9 is even slower than V7 was. Same # of tuners, same lineups yet my startup time has almost doubled.

I am finishing up a massive optimization for Carny that I will be submitting soon to the core project. It took me from 6 minutes for full init on startup down to 2 seconds which then makes limited init almost pointless. Through verification I can also say that the results were exactly the same as what I would have seen via the "long" way. This is achieved by making maps of airings based on what the agents will want to look up instead of processing each airing sequentially across all of the agents. It's also multi-threaded which gives it an additional boost that's almost linear on the quad core I am testing on.

[wayner]

(This seems to be the Wayne thread so I guess I have to contribute)
I don't have excessive startup times despite the fact that my primary system has been running for many years. Perhaps it is because I don't use Intelligent Recording?

[KryptoNyte]

Originally Posted by EnterNoEscape

I am finishing up a massive optimization for Carny that I will be submitting soon to the core project. It took me from 6 minutes for full init on startup down to 2 seconds which then makes limited init almost pointless. Through verification I can also say that the results were exactly the same as what I would have seen via the "long" way. This is achieved by making maps of airings based on what the agents will want to look up instead of processing each airing sequentially across all of the agents. It's also multi-threaded which gives it an additional boost that's almost linear on the quad core I am testing on.

Holy crap - that's some solid work right there.

[waynedunham]

Originally Posted by wayner

(This seems to be the Wayne thread so I guess I have to contribute)
I don't have excessive startup times despite the fact that my primary system has been running for many years. Perhaps it is because I don't use Intelligent Recording?

I'm relatively sure that it is. I just can't see using that speedy setting if it delays SageTV setting up IR recordings up to 7 hours. In my use that is just WAYYY too long.

I wonder if it is the same reason that if I watch and then delete a favorite recording it will record the same episode again (as a favorite, not an IR) even though it is marked as watched if the next airing comes in about a 7 hour window? If I leave the watched episode and don't delete it, SageTV won't record the episode again in that approx. 7 hr window.

[waynedunham]

Originally Posted by EnterNoEscape

I am finishing up a massive optimization for Carny that I will be submitting soon to the core project. It took me from 6 minutes for full init on startup down to 2 seconds which then makes limited init almost pointless. Through verification I can also say that the results were exactly the same as what I would have seen via the "long" way. This is achieved by making maps of airings based on what the agents will want to look up instead of processing each airing sequentially across all of the agents. It's also multi-threaded which gives it an additional boost that's almost linear on the quad core I am testing on.

I'll eagerly await this new code. If it cuts my startup times to a reasonable time even with IR I will send you many virtual beers! (and many real ones should we ever meet)

Interesting reading that linked thread where you and Narflex are discussing the changes. I about fell out of my chair when I saw this from Narflex "It takes about 1.5 days for Carny to
run a full cycle on my DB because it has 15 years of history in it. :-)"

My DB goes back many, many years as well. It might even be the same one that started back when I first installed SageTV (ver 4 if I recall)

I will say this. On both of my servers when I first changed over to Schedules Direct it threw IR into a tizzy marking literally hundreds of programs (Hey, this guy has 9 tuners, let's see if we can keep them all full, all the time!). Probably the biggest round of marking things "Don't Like" I've ever had, even the first time I turned IR on back in the day.

[wayner]

Originally Posted by KryptoNyte

Holy crap - that's some solid work right there.

Agreed - well done. Is there something similar that could speed up media file scanning. That can take forever if you have lots of media files.

[egeller]

Originally Posted by EnterNoEscape

I am finishing up a massive optimization for Carny that I will be submitting soon to the core project.

ENE
This sounds exciting. Do you have any idea as to when it will it be released into the wild?

EG

[EnterNoEscape]

Originally Posted by egeller

ENE
This sounds exciting. Do you have any idea as to when it will it be released into the wild?

EG

I'm also updating the change log with everything I have added and others have added to date. There have been a few good things fixed in 9.0.15, so I'll probably ask for a new release a week after committing just so that I can break it in more and see if I have any horrible problems with the new code. I suspect not and for once the upgrade doesn't come with database changes, so you could go back to 9.0.14 without any real problems should things be horribly broken for you.

[EnterNoEscape]

Originally Posted by wayner

Agreed - well done. Is there something similar that could speed up media file scanning. That can take forever if you have lots of media files.

Media file scanning takes a while for very different reasons, so I doubt we can enhance that by much. In Carny, we were just being extremely inefficient because the desired data couldn't be easily reduced to a few thousand hashes. With files, I don't think we're doing anything that could be optimized in a similar way.

[wayner]

The thing that seems to take a long time is music files - because you tend to have tens of thousand of those compared to far fewer video files. It would be nice if you could do scans by type of media - video, photo, music. That would help a lot as this generally hits me when I add a new video file, I have to start a scan and wait 5 minutes or so to finish. Then I often have to make some changes/corrections to metadata if it didn't scrape correctly.