so that the networked file system will run faster
Just out of curiosity, why this system structure?
This is for an "internal" wiki, just so everyone at home can share a few common notes, or lists of procedures on how to fix things.
Overall it's an unusual setup - there's a pair of Debian virtual systems, in an HA configuration, that have /usr/share/dokuwiki and /var/lib/dokuwiki running on a networked "share", which is run using GlusterFS, and is also running on a pair of virtual systems. So any single virtual system can break, or the host running one of the Apache2 servers and the backend gluster servers can break, and the wiki should just stay up.
Partly this is just to see if it will work - I do realise this is non-standard.
Partly this isn't as though an internal wiki needs this kind of resilience and uptime, but it means various components on the network can die and the wiki will stay up - as it can take a while before I've either got the money to replace something, or the time to rebuild something.