<p>I just read up on a performance of LINQ, and there is a HUGE amount to be gained by using Compiled LINQ.</p>

<p>Now, why won't I always use compiled LINQ?</p>

[{'answer_id': 8152, 'author': 'Patrick', 'author_id': 429, 'author_profile': 'https://Stackoverflow.com/users/429', 'pm_score': 3, 'selected': True, 'text': '<p>Short answer: when it\'s only going to happen once in a long time.</p>\n\n<p><a href="http://blogs.msdn.com/ricom/archive/2008/01/14/performance-quiz-13-linq-to-sql-compiled-query-cost-solution.aspx" rel="nofollow noreferrer">Long Answer</a>.</p>\n'}, {'answer_id': 36373593, 'author': 'madhur mukhi', 'author_id': 6148954, 'author_profile': 'https://Stackoverflow.com/users/6148954', 'pm_score': 0, 'selected': False, 'text': '<p>You should use it when some linq query is executing most of the time. Those can be converted to compiled lynq. Performance will be improved as execution path of query will be set at compile time. I used it in my project and performance went up a notched.</p>\n'}]
['https://Stackoverflow.com/questions/8142', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/380/']