About Fusers

PhotoMesh can take advantage of computer clusters to accelerate database creation. Fusers allow you to share the demanding processing requirements of the different build steps (data preparation, AT, point cloud, mesh model, texture, 3DML/other outputs) between several computers on the same network. The master computer utilizes the computing power of the network’s client computers by connecting to PhotoMesh fusers on the client machines.

The fuser remains idle until used by the master computer on the network. Once started, the fuser runs on the client machines, with only an icon in the system tray that opens a status log and a dialog to stop or suspend fusers. You can install the PhotoMesh Fuser on the same computer with the PhotoMesh Build Manager and/or on other computers.

In addition to standard fuser use, PhotoMesh also offers two options for auto-scaling of fusers to enable dynamic allocation of fusers based on project requirements:

§  Amazon Web Services (AWS) Fusers – AWS fuser instances can be dynamically launched whenever there are unassigned pending fuser tasks, to further accelerate model creation.

§  Fusers Pool – Fusers can be shared between several PhotoMesh Build Managers in your organization, enabling each machine running PhotoMesh to use the combined resources of all the machines in the pool. A distributed management approach is used to manage the pool fusers, whereby each PhotoMesh Build Manager manages its own fuser needs and resources by requesting fusers from the pool when generating a build and returning the fusers when they are no longer needed.

When beginning the build process the PhotoMesh Build Manager application determines what build steps are required and assigns them to the different fusers. PhotoMesh Build Manager continuously monitors the fusers’ progress and assigns new processing tasks based on fuser availability.

Both PhotoMesh Build Manager and the PhotoMesh fusers require read-write access to the working and project folders.