NFS uses the standard filesystem caching, the Native GlusterFS uses up application space RAM and is a hard-set number that must defined.
If you look at the documentation
The FUSE client allows the mount to happen with a
round robin style connection. In
/etc/fstab, the name of one node is used; however, internal mechanisms allow that node to fail, and the clients will roll over to other connected nodes in the trusted storage pool. The performance is slightly slower than the NFS method based on tests, but not drastically so. The gain is automatic HA client failover, which is typically worth the effect on performance.
So in summary: It depends on the requirements. When there is enough RAM available on the system and performance is not overall important
FUSE seems to be the better choice.