- Author: John Ed Quinn
- Date: 2021 March 01
- The object used can be found here by searching for Buckyball.
- Executing POVray directly, using the following resolutions, we can determine the amount of time needed to render a single video frame:
- 320x400: 0.901s
- 640x480: 1.186s
- 1280x720: 1.870s
- 1920x1080: 2.877s
- Below is the estimate (based on the preliminary results above) for how long it would take to render a minute-long video at 10 frames per second for the following resolutions.
- 320x400: 540.6s
- 640x480: 711.6s
- 1280x720: 1122.0s
- 1920x1080: 7726.2s
- At each run of
condor_povray
, in the order from 320 to 1920, the time between submission and first execution becomes greater and greater. This may have been due to resource limits and additional condor submissions across the condor pool at Notre Dame.
- Log file can be found here
- The corresponding Condor Analyzer page can be found here
- At the peak of the distributed computation, 120 jobs ran at once.
- For the most part, the computation ran smoothly. There was a steady completion of jobs, with a small number of jobs taking longer than usual (causing the completion to not be perfectly linear) towards the end of the run.
- The total elapsed time was 208s.
- Log file can be found here
- The corresponding Condor Analyzer page can be found here
- At the peak of the distributed computation, 115 jobs ran at once.
- For the most part, the computation ran smoothly. There was a steady completion of jobs, with a small number of jobs taking longer than usual (causing the completion to not be perfectly linear) towards the end of the run.
- The total elapsed time was 229s.
- Log file can be found here
- The corresponding Condor Analyzer page can be found here
- At the peak of the distributed computation, 120 jobs ran at once.
- For the most part, the computation ran smoothly. There was a steady completion of jobs, with a small number of jobs taking longer than usual (causing the completion to not be perfectly linear) towards the end of the run.
- The total elapsed time was 389s.
- Log file can be found here
- The corresponding Condor Analyzer page can be found here
- At the peak of the distributed computation, 120 jobs ran at once.
- For the most part, the computation ran smoothly. There was a steady completion of jobs, with a small number of jobs taking longer than usual (causing the completion to not be perfectly linear) towards the end of the run.
- The total elapsed time was 384s.