Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
Wrap Up1:39 with James Churchill
Let's wrap up this workshop with a quick overview of what we didn't cover and some final advice on performance optimization.
Additional Application Debugging, Tracing, and Profiling Resources
For more information on debugging, tracing, and profiling .NET applications, see this section of the official Microsoft docs:
A Deeper Look at EF Performance
For a deeper look at EF performance—including a look at query plan caching, metadata caching, and query compilation—see this Microsoft white paper:
Application performance profiling and optimization is a big topic. 0:00 It'd be impossible to try and 0:04 cover every possible scenario that can arise when developing a web app. 0:05 Given that, our goal is to give you the tools that you need in order to identify 0:10 and debug performance problems on your own. 0:14 While this workshop specifically dealt with EF query performance, 0:17 there are many other types of performance issues that 0:21 can arise when developing ASP.NET MVC web apps. 0:24 See the teacher's notes for links to additional performance profiling and 0:27 debugging related resources. 0:31 Also, there are advanced strategies for 0:33 improving the performance of VF we didn't cover in this workshop, 0:35 including query planned caching, metadata caching and compiling queries. 0:39 Again, see the teacher's notes for more information. 0:45 Sometimes performance problems don't need to be fixed. 0:48 Instead of rewriting queries, or 0:52 implementing a cache, you can rethink the design of the application and 0:54 refactor your code in order to completely sidestep the performance issue. 0:58 Even better, 1:03 that'll often result in a simpler solution which will be easier to maintain. 1:03 When thinking of performance optimization be sure to consider developer performance. 1:08 Sometimes it's better to keep code as simple as possible, 1:13 even if a more complex version performs better, in order to make it easier for 1:16 developers working on that code. 1:21 And avoid the temptation to prematurely optimize your code. 1:23 If you optimize too early, you might find your 1:28 work going to waste as features are removed from the application or replaced. 1:30 Good luck with your performance debugging. 1:35 We'll see you next time. 1:37
You need to sign up for Treehouse in order to download course files.Sign up