...
To further explain and understand the 3Delight Cloud rendering charge, we will use this simulation of four independent renders at various stages:
Four independent renders shown in the 3Delight Cloud dashboard (in 3Delight Display).
...
Syncing | The first render is at the “Syncing” stage. This is when the scene elements are uploaded to the cloud. There is no charge during that process. This can be quick or long depending on the speed of your internet connection and how many of your scene elements are already cached in the cloud. For the entire duration of that process, the 24-core minutes counter and number of cores are marked as “ - – “ and the progress bar does not start. This serves as a confirmation this is not charged. |
Parsing, Rendering | The 3rd and 4th renders illustrated renders at various stages of rendering while the number of 24-core - minutes are counted. This will end up to be the charge for the rendering. As explained before, the rate of increase of the counter is proportional to the number of cores used. While the 24-cores-minute counter is shown in the dashboard as an integer, the underlying value is precise to the second. Prior to Parsing, there is a varying Starting time that stage with a duration that varies depending upon the global 3Delight Cloud usage condition. It can last up to 30 seconds but it is only . But in order to offer a predictable and uniform charge, this is counted as a fix 0.3 x 24-core-minute (i.e. 18 secs) regardless of how long it takes. We are aiming to reduce this further in the future in order to keep this negligible even when thousands of cores are used. |
Completed | The last render (shown in a subdued shade) is a completed one. As such, the 24-core-minute counter has stopped. It is possible at that stage the image is still being progressively displayed on your screen. This would happen if your internet speed could not keep up with the rendering speed. In this instance, the fact the 24-core-minute counter has stop to increase serve to confirm stopped serves as a confirmation that the process of image transmission is not charged. |
...
- 10:02pm is the time the render was completed. This is unlike the dashboard which shows when the time it has started.
- 46s is the real time it took to render the image, including data Syncing. This complimentary information has no incidence on the cost.
- 712 cores is the average number of cores used during the rendering (including the starting and parsing stages).
- Rendering time is calculated precisely in minutes and seconds (precise to the second). The seconds are not shown in the dashboard106m 02s is the charge, the rendering time in 24-core-minute calculated precisely to the second (including the starting and parsing stages).