Can you explain us the prices?

[bepeg4d]

Hi mirobimbo,
yes of course, as you can see OctaneEngine is a similar but different product oriented to subscription for those that need it, for example, you can subscribe for a month if you need a net render slave only for a limited time
It's not a substitution but an integration of OctaneRender to enlarge the ecosystem
ciao beppe

[coilbook]

Can anyone explain what this means "The GPUs should be 20 x 40 octanebench = 800 octanebench power per 1000 minutes. "

[coilbook]

1000 GPU minutes meaning ?
1. I am given one 780Ti and I can render with it for a 1000 minutes
2. Or I can chose 1000 780TIs and will be given one 1 minute of render time.

What if I need more render time. How much is it after 1000 minutes another 10 bucks per 1000

[bepeg4d]

mark0spasic is correct, looking again at the slide, 1000 minutes x 1GPU = 40 OctaneBench = 50 minutes x 20 GPU = 800 OctaneBench = 9.99$
sorry for the confusion

@ coilbook: I guess it's one Tesla @ ~40 OctaneBench x 1000 minutes or 20 Tesla x 50 minutes
ciao beppe

[xcaseyx]

so for 19.99 a month I can network render on every GPU on my network?

if I have 90 workstations with 2 gpus in each, can I render with 180 gpus on 1 machine? Do we have the GPU limits of octane 1.5 back?!

this is freaking huge if thats the case.


~ WHAT IS THE SINGLE SEAT GPU LIMIT FOR OCTANE 3.X for 19.99 a month?

[coilbook]

Does anyone know how many octanebench power I have when I got 12 x 780TIs ?

Thank you

[kavorka]

Does anyone know how many octanebench power I have when I got 12 x 780TIs ?

Thank you

You can check it out here:
https://render.otoy.com/octanebench/

[Lewis]

Arghh, so much confusion, they've should post more clear info about all this .

Let's hope May 15th all will be clear.

[Goldorak]

I will post with more detailed guidance on the pricing based on your questions as they come in.

To clarify, yes, you can roughly translate a $9.99 bucket of ORC credits to an hour of rendering on a GPU box with 800 OctaneBench - but that is not really the whole picture when it comes to ORC. It is however the simplest reference we can give users to compare what cloud $ spent mean relative to local rendering in a way they are used to.

The main thing to consider when using ORC is to understand that it scales in parallel when it comes to animation/multiple frames - that's what it's designed for. Maybe your Octane render box is at or better than 800 OctaneBench when rendering a frame. But ORC can render hundreds, even thousands of frames all at once at this speed.

From a cost savings perspective, ORC is also designed to bill you in granular chunks, based on the work a single GPU does in a minute so no money is wasted if a render doesn't fit into one hour chunks.

We are considering adding a utility that calculates the cost of finishing a frame on ORC as you are rendering locally (logical as we can snapshot and render to ORC as eell). We can also run a cost estimator that does this on ORC itself but as this costs money (maybe a few % of the final render cost) we weren't sure if this would be worthwhile relative to local estimation at no cost.

[Goldorak]

1000 GPU minutes meaning ?
1. I am given one 780Ti and I can render with it for a 1000 minutes
2. Or I can chose 1000 780TIs and will be given one 1 minute of render time.

What if I need more render time. How much is it after 1000 minutes another 10 bucks per 1000

Regarding 1/2 above - ORC is designed to get you renders back within a few hours for most jobs, so the end result is not very different if you are talking about a single frame. As I mentioned earlier, multiple frame or multi-segment jobs are the ones that scale best on ORC.

In addition to pre-paying for more render credits, we are looking into recurring billing (like Skype credits) where we keep charging you in $10 inc. up to a max limit you can specify in your subscription.

If you run out of credits in the middle of a frame, and don't re-up, then you can still download the Octane film buffer and finish it locally - that is why this feature was important to get in place launch, as it ensures your cloud renders on ORC are never useless. They can always be finished off cloud with local rendering, even per frame.