The Job Server¶
When an interval is Executed inside of HoloEdit, each individual asset required by the Job Server will be exported and uploaded for processing. A progress bar will appear in your HoloEdit window to track the upload status.
Once upload is complete, you can continue editing your Composition in HoloEdit, and even save and exit your Composition. As long as the job isn’t cancelled, as soon as the job server has completed processing a work item, its results will be imported back into an appropriate HoloEdit Composition. When HoloEdit detects a completed work item, it will pause briefly to fetch the job results and apply them to the corresponding Interval.
If a Work Item is completed while a Composition is closed, the appropriate files will be fetched as soon as you open the Composition.
Choosing a Job Server¶
You can change your job server at any time by selecting either “Local Job Server” or “Remote Job Server” from the Tools menu. Any jobs in progress will not transfer to a new job server, and will need to either be re-submitted or fetched from their original job server after completion.
HoloEdit defaults to using the Remote Job Server, and the Stages available in HoloEdit are designed with the power of cloud computing in mind.
The Local Job Server saves time on upload and download, and can be sufficient for small jobs and quick processing of larger meshes.
Samples produced by completed Jobs are stored on the Job Server. As soon as a Composition with the matching job is opened, HoloEdit will contact the job server and retrieve the appropriate data.
This process is called “Fetching” jobs, and applies whether the Composition was left open while the job completed, or closed and then reopened to fetch the results at a later date. Remote Job Server results are re-downloaded every fetch.
When a Composition is saved with results that have already been fetched, those results are stored locally to that Composition and are accessible without repeatedly fetching the results.
Local Job Server results are fetched the same way as Remote Job Server results, but are stored locally in the JobAPI/Temp folder located in your HoloEdit 2021.2 installation directory.
Local Job Server¶
Starting the Local Job Server will launch a PowerShell and npm based server on your local computer. Both of these programs are required for the local job server, and should not be closed manually until you close HoloEdit or change Job Server.
First Time Setup¶
The Local Job Server will install and initialize the required components when it’s activated, but in case of errors or changes to your HoloEdit installation, this process can be manually re-run by choosing the “Run First Time Setup” option in the Tools Menu.
Remote Job Server¶
The Remote Job Server executes jobs on Cloud Servers provided by Arcturus. When a Job is dispatched to the Remote Job Server, it will be uploaded after export and fetched after the job is completed.
Processing on the Remote Job Server a valid HoloEdit License and consumes Compute Hours associated with your account. Your organization’s remaining Compute Hours are listed in the User Profile window, accessible from the User -> Manage Profile option on the Menu Bar.
The amount of Compute Hours consumed per job can be previewed in the Compute Time column of the Job Viewer window.
Different Stages and files consume different amounts of Compute Time per process, so you should be sure to keep track of the most costly operations in your projects.
The compute time cost of many stages varies by triangle count. Try to minimize Compute Time by using the Clean Mesh Stage to reduce polygon count before processing your Clips.
If your account has no remaining Compute Hours, you will no longer be able to submit jobs to the Remote Job Server. Jobs in Progress will finish currently processing work units but will not start any new work units. To purchase more compute hours, contact firstname.lastname@example.org
Compute Hours and your HoloEdit license¶
Compute hours expire in 30 days after your HoloEdit license has lapsed. If you renew your HoloEdit license within 30 days of expiration, your compute hours remain in your account.
Jobs are currently placed in a first come first serve queue. If all active compute nodes are in use, new jobs will not begin processing until existing jobs are completed.