6587b4dcef
* Feature: support for shared downloads directory This feature is especially relevant for users with several clients running simultaneously within the same computer (computers running several GPUs or any combination of GPUs + CPUs) or multiple computers running in a network. The feature allows the user to specify a shared downloads directory via the new -shared-downloads-dir client option. All the clients using that option will share the same binaries and scene files. How it works? The first client downloading a binary or scene will save the file in the directory especified in -shared-downloads-directory. The rest of the clients using the same option will wait until the file has been downloaded. Once the file has been downloaded, it will be ready for the rest of the clients. This feature is especially relevant for users with metered/slow connections or multiple computers/clients that don't want to download the same binary/file multiple times. IMPORTANT: All the clients intended to share the binaries and scenes must execute the client with the same -shared-downloads-dir parameter.
SheepIt Render Farm Client
Overview
SheepIt Render Farm Client is an Open Source client for the distributed render farm SheepIt.
Compilation
You will need Java 1.8 or higher. (OpenJDK and Oracle are both supported).
To create the jar file, simply type ./gradlew shadowJar on linux/OSX and gradlew.bat shadowJar on Windows in the project's root directory.
Usage
Once you have the jar file, you can see how to use it by running:
java -jar build/libs/sheepit-client-all.jar --help
When you are doing development work, you can use a mirror of the main site specially made for demo/dev. The mirror is located at http://sandbox.sheepit-renderfarm.com, and you can use it by passing -server http://sandbox.sheepit-renderfarm.com to your invocation of the client.
At the command line ui (-ui text / -ui oneLine) you could type in the following commands and press enter to control the client:
- status: get the current status of the client (paused, stoped, etc.)
- priority : set the renderer process priority
- block: block the current project
- pause: pause the client to request new jobs after the current frame has finished to render
- resume: resume the client after it was paused
- stop: stop the client after the current frame has finished
- cancel: cancel the stop request
- quit: stop the client directly without finishing the current frame