Server-Side-State-Saving vs Client-Side-State-Saving in JSF
Client side state saving needs the state to be serialized, encrypted and base64 encoded. Saving state on the client uses more bandwidth as well as more client resources, while saving it on the server uses more server resources. You may also want to save state on the client if you expect your users to disable cookies. By default, the state is saved on the server. If state is saved on the client, the state of the entire view is rendered to a hidden field on the page.
In server side state saving by default in MyFaces, the state is serialized but not encrypted or base64 encoded. It is possible to disable serialization in MyFaces and make it faster.