title: Does adding redundant @JsonProperty value annotations to fields increase deserialization performance?
body: <p>I'm using Jackson (2.6.0) to deserialize JSON requests into simple POJOs. I have implemented all the setter methods in my POJOs to fine tune the assignment. Some of the field names in the JSON are rather cryptic, such as <code>seq</code>. I'd like to name my java class field something like <code>layoutSequnce</code>.</p>
  
  <p>I'm aware to do this I simply need to annotate my field as:</p>
  
  <pre><code>@JsonProperty("seq")
  private int layoutSequence;
  </code></pre>
  
  <p>My question is for JSON fields I do not needto rename, such as <code>title</code>, is there any minimal performance advantage to annotating it anyway as:</p>
  
  <pre><code>@JsonProperty("title")
  private String title;
  </code></pre>
  
  <p>My question stems from my understanding of how I think Jackson works behind the scenes. I'm assuming Jackson uses reflection to introspectively examine my POJO and identify the current field it's attempting to assign from the JSON value. With this approach, I'm assuming it has to do some searching to find a match, which has some small amount of overhead.</p>
  
  <p>If I specify the field name directly, will Jackson just blindly attempt to initialize my field using a setter that matches the pattern of the field name (<code>setTitle()</code> in this example) I've identified in the annotation? Or does it still perform an internal class search to validate the method's existence?</p>