Links

8. Nodes Receive and Process Frames

Node Operators receive their job parts, process them and send results (rendered frames) back to RNDR Network.
Process Flow for Nodes: Download an executable program from OTOY’s website → input your wallet ID and run application → connect to RNDR → look for jobs → download scene to system memory → render & periodically send status back to central server → report job complete → upload to storage server → check node availability → repeat cycle
Here is a short description of the steps involved for the nodes to download and run the RNDR token application:
  1. 1.
    Access the URL provided by the RNDR network in onboarding process.
  2. 2.
    Once prompted, fill in the credentials sent by the RNDR team.
  3. 3.
    You’ll be directed to a screen with the client link. Click the Download button and wait for the .exe file to install.
  4. 4.
    A screen pops up for users to enter the ETH wallet ID they wish to receive the tokens in. The same wallet IDs are used to identify node-operators. RNDR does not own or hold any information in regards to these wallets, they are accessed by Metamask.
  5. 5.
    Click Close and that’s it! The RNDR Token application will start running.
After completing these steps, nodes are now in the network and can pick up frames from submitted jobs.
Those who contribute GPU processing power can see the progress of each frame, the frame number from the scene, and the status and utilization of the GPUs and VRAM (free VRAM vs. used VRAM).
While the application is running, it shows different messages for the node:
  • Downloads done: Downloading to memory. In this particular workflow, each frame is downloaded one step at a time.
  • Sha256: Verification hash function.
  • Node waiting on message/Node message received: A node is waiting on a job to be posted/ A job was sent to the node.
If the node‘s administrator decides to close the application during rendering, it will render the last frame and send it back to the creators before it closes the application. Be aware that this is only if they exit from the system tray; you can close the window and rendering will not be interrupted.
The node client will reuse assets when it can once those scene assets are held in local node memory. This minimizes setup time and improves the rendering to general work time ratio. The node wants to hold onto as much as possible for later work, and there’s some intelligence about when it downloads assets vs clearing out what is unlikely to be reused.