Reply to thread

Message

<blockquote data-quote="sean2078" data-source="post: 70456" data-attributes="member: 23956">ngen will help only just after you install MediaPortal, but it does help.&nbsp; .NET 2.0 ngen is much improved over .NET 1.1 ngen.&nbsp; Mainly because in 1.1 each time a dependency was changed, the entire dependency chain had to be JIT'ed again.&nbsp; Generally speaking (and I'm not a MediaPortal engineer) there shouldn't be much need to run ngen at the end of install.&nbsp; It wouldn't hurt, but in terms of supporting it, it definitely shouldn't rank high at all on the priority list.In terms of experience, sure - there's always going to be a difference between an exe that's been ngen'ed (or JIT'ed) and the same exe that hasn't been JIT'ed yet.But the point is that as soon as you run the app once, running ngen on any of the components again won't speed up anything.&nbsp; Also running it just after install won't speed up the app any more than it would perform the 2nd time you run MediaPortal.&nbsp; Also, MS is attempting to get the 2.0 framework optimizer service on everyone's Win. installation and if that's running, it will automatically ngen MediaPortal for you whenever your computer is idle.Personally, I would like engineering time to be spent on more important items.Hope that helps.</blockquote>

[QUOTE="sean2078, post: 70456, member: 23956"] ngen will help only just after you install MediaPortal, but it does help. .NET 2.0 ngen is much improved over .NET 1.1 ngen. Mainly because in 1.1 each time a dependency was changed, the entire dependency chain had to be JIT'ed again. Generally speaking (and I'm not a MediaPortal engineer) there shouldn't be much need to run ngen at the end of install. It wouldn't hurt, but in terms of supporting it, it definitely shouldn't rank high at all on the priority list. In terms of experience, sure - there's always going to be a difference between an exe that's been ngen'ed (or JIT'ed) and the same exe that hasn't been JIT'ed yet. But the point is that as soon as you run the app once, running ngen on any of the components again won't speed up anything. Also running it just after install won't speed up the app any more than it would perform the 2nd time you run MediaPortal. Also, MS is attempting to get the 2.0 framework optimizer service on everyone's Win. installation and if that's running, it will automatically ngen MediaPortal for you whenever your computer is idle. Personally, I would like engineering time to be spent on more important items. Hope that helps. [/QUOTE]

Verification