It really depends.
Benefits of a Local File
- You are in control of the file. You decide what is used, what version and any changes require you to explicitly change the file.
- The file is already on your server. There is no need for an additional request to an external source that may / may not be available. This is important if your app may possible be accessed in an intranet or non-connected environment.
Local files will enable you to do things like "bundling" multiple of your own files and dependencies together and then optimizing them into a smaller single file. This is very useful if you have other things that depend on jQuery (like Bootstrap, etc.).
Benefits of a CDN
- No Server Overhead or Bandwidth Constraints. Since you aren't serving the file yourself, you don't need to worry about how many users are going to be downloading it as it isn't coming from you at all.
- Caching and Smarter Serving. CDNs generally take heavy advantage of caching, which can typically speed things up for users. CDNs also are geographically distributed and can handle serving users from around the globe as opposed to your server serving from a single location.
CDNs will really shine if you are going to be expecting a large amount of traffic to your site from a diverse distribution of users. They can also save you quite a bit if you actually have to pay for the amount of bandwidth you use as serving an ~80k jQuery file to 1 million users per day would add up, whereas a CDN would handle that burden for you.
Resources
You might consider reviewing over a few of the following resources to get a bit of insight from others that compare the pros and cons of each of these options to determine what might be best for you :