Tell me something about Apex Governor Limits?

 
Visualforce pages that usually contain a form part additionally include the hidden form field and encrypted field that exemplifies the page’s view state. This view state is consequently created, and as the name recommends, it holds the page state – the state that incorporates the parts, field values, and the controller state.

Best Practices to lessen the view state size

1. Minimize the number of forms on the page. Utilize apex:actionRegion as opposed to utilizing at least two forms.
2. Refine your SOQL just to retrieve the information required by the page.
3. All private and public data members in the Custom, Standard, and Controller extensions are saved.
4. Mark any of the Apex variables that is not important to the view state as Transient. (The transient variables are not merely passed to see state and consequently not put away in View State)
5. Create wizards with as few pages as could be expected under the circumstances
6. Use outputLink parts rather than commandLink or commandButton segments where conceivable as they don’t should be settled in shape.