steven/cyclescaler
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update 'README.md'

Browse Source
This commit is contained in:
Steven Polley 2020-05-21 06:03:03 +00:00
parent 397fee24e1
commit 18dd8fb148
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -4,7 +4,11 @@
Containerized, distributed blender rendering - cloud-native alternative to Blender's network based rendering. Containerized, distributed blender rendering - cloud-native alternative to Blender's network based rendering.
Cyclescaler is an easily scalable rendering system for the Cycles 3D rendering engine built into Blender. It's incredibly easy to spin up instances on all platforms which support containers including all the good cloud providers. You can also easily run it on premises with a Kubernetes cluster or as standalone containers with docker-compose (examples provided). It's built on the following technologies: #### What is Cyclescaler
Cyclescaler is an easily scalable rendering system for the Cycles 3D rendering engine built into Blender. It's incredibly easy to spin up instances on all platforms which support containers including all the good cloud providers. You can also easily run it on premises with a Kubernetes cluster or as standalone containers with docker-compose (examples provided). It will even run on ARM processors. The idea is that you can use the scalability of cloud providers which allows you spin up thousands of instances momentarily to quickly render the job in parallel.
Cyclscaler is built on the following technologies:
* The Go Programming Language - https://golang.org/ * The Go Programming Language - https://golang.org/
* Docker - https://www.docker.com/ * Docker - https://www.docker.com/
@ -17,7 +21,7 @@ Cyclescaler is an easily scalable rendering system for the Cycles 3D rendering e
The project is broken into two parts: The project is broken into two parts:
* Master - This can be thought of as the server, it's the portal that users interact with to upload .blend files and tweak render parameters. * Master - This can be thought of as the server, it's the portal that users interact with to upload .blend files and tweak render parameters.
* Slave - This can be thought of as a client, and it handles rendering the images which get stitched together to create an animation. There can be as many instances of the slave as you want, the more slaves, the more simultaneous * Slave - This can be thought of as a client, and it handles rendering the images which get stitched together to create an animation. There can be as many instances of the slave as you want, the more slaves, the more simultaneous frames can be rendered.
![alt text][logo] ![alt text][logo]