Can you explain us the prices? Tweet

[coilbook]

so basically 6 x 980 TI cards to render for one hour will cost you 10 dollars, That's too expensive and you do not get that many cards.

I would pay this much per hour if I was given like 200 GPUs where you can see fast results like 5 seconds per frame. We currently have 12 X 780TIs and even using just AO it still takes 2-3 minutes per frame. That means if we are given 800 octanebenchmarks per hour for $10 we can only render 20 - 30 frames

maybe one day cloud rendering will be cheap enough where you get 200-300 GPUs for as much as you want and you pay 500 bucks a month for service.

now all hopes to pascal GP100

[Goldorak]

so basically 6 x 980 TI cards to render for one hour will cost you 10 dollars, That's too expensive and you do not get that many cards.

I would pay this much per hour if I was given like 200 GPUs where you can see fast results like 5 seconds per frame. We currently have 12 X 780TIs and even using just AO it still takes 2-3 minutes per frame. That means if we are given 800 octanebenchmarks per hour for $10 we can only render 20 - 30 frames

maybe one day cloud rendering will be cheap enough where you get 200-300 GPUs for as much as you want and you pay 500 bucks a month for service.

now all hopes to pascal GP100

Pascal may be a amazing and we'd love to see that double speed of local rendering.

ORC is not (at this time) intended to replace your local GPUs for single image rendering or small animations (< 50 fames) . But when you have thousands of frames, taking weeks to render even on 20x Titan X's, then ORC is really useful.

ORC works differently than current local/network rendering when it comes to animation jobs. Frames are rendered in parallel on ORC when possible, not linearly.

As a rule of thumb, you should send ORC 100+ frames per job. In this case, ORC is going to spread all frames across dozens, 100's, or even 1000s of GPUs to complete all frames in minutes, not hours.

Using your case as an example, if it takes an hour to render 20 frames of your scene on your local machine @ 800 OB, ORC will try render each of those 20 frames in parallel, and complete all 20 frames ~3 minutes.

This means ~16,000 OB would be applied in 3 mins, per your $10 bucket. At this rate, ORC will be rendering 400 frames/hr , or ~9 seconds/ frame at a cost of 50 cents per frame. To render more > 20 frames, you turn on recurring payment buckets (+$9.99 increments), and set a max monthly cap that fits your needs.

Let's say you decide to set this cap at $500/month. This would allow you to render 1000 frames in ~150 minutes. To be clear, we manage and queue many thousands of jobs per day at this rate, so ORC is optimized to deliver same day results at this volume, assuming peak usage.

Worst case, if your ORC budget is spent mid-render, before a frame reaches its final sample count, your partial render is paused and the filmbuffer is saved. The render can be resumed later on ORC by adding more credits. Or you could download the film buffer and complete the render locally without spending any further money on ORC.

Pause/resume rendering across both cloud and local renders (via 3.00 film buffer files) means any money spent on ORC render jobs can at minimum be used to augment and granularly complement local GPU rendering power.

[kavorka]

So, assuming our local network has 800 Octane bench (ours is 730, so close) and we have an animation to render and it will take 3 days to render fully. We could get the job done in a couple of hours for $720 (72 hours at $10 per 800 Bench hour)?

how do we know how many GPUs are available to render in parallel? Does it use what is available? So if there are a lot of jobs rendering at the same time, we might not be able to use as many cards to get it rendered as quickly as we might want.

The cost seems reasonable as a fail safe but does not seem viable for most studios to use on a regular basis.

If we can really use 1000s of cards at once, it could be useful because It would allow us to spend more time working and not have several days before the deadline to hit the render button. However, I am apprehensive (for now) to rely on the cards being available at the time I need them.

One more question. is the limit per frame the 800 OctaneBench, or can you scale that up? We often do very large brochure images that take about a day on our network. Since our network is 90% of the 800 OctaneBench, it would be 10% faster to render it on the cloud (minus upload and download times), but wouldnt really help us in a pinch. If we could scale that up on one frame and our client needs it "now" we could put some of that cost on them and get them what they need as soon as they need it.

[coilbook]

ok thanks for explaining now i got it. basically it is 800 ob bucket that can be done in one hour (more time is given but slow rendering) or 3 minutes (less time but very fast ) but same price for 10$

Hopefully price will drop one day. I think if you guys can reduce it to 3$ a bucket you will have way more customers. $15 dollars per one second of rendered animation is way too pricey So if we need to make a short cartoon that is 10 min long it would cost us $9000 dollars to render. That's WAY too expensive for small studios and artists. I can buy 18 good video cards

i just did a sample CPU cloud rendering pricing. It would only cost 1000$ to render 10 min of animation at the rate of 10 min per frame and the whole job would be done in 13 hours on their 50 rebus farm nodes

[coilbook]

here is another example for $10000 I can get 20 x 12 core machines unlimited use for the whole month (CPU)

https://www.rendercore.com/monthly.html ... gQod1aoH0A

[glimpse]

coilbook, for 9-10k You can build 7GPU system that would give You 6GB of vram & ~1000 in terms of Octane bench & You can render for years..but.. You need to do that investment..& if You can put workloads to keep it bussy most of times..then it makes sense.

[Rik]

Ahh. Sorry, still not overly clear.

How about a couple of simple examples;

Takes me say 1 hour to locally render an image using 3 gtx580(~200octane bench) How much and how long using ORC?

Takes 10 hours to locally render a 1000 frame animation using 3 gtx580(~200octane bench) How much and how long using ORC?

And am I right in assuming there will be a simple "render it whizzy fast in the cloud" button below the "open octane render viewport" button in 3ds Max?

[WalterSulivan]

Ahh. Sorry, still not overly clear.

How about a couple of simple examples;

Takes me say 1 hour to locally render an image using 3 gtx580(~200octane bench) How much and how long using ORC?

Takes 10 hours to locally render a 1000 frame animation using 3 gtx580(~200octane bench) How much and how long using ORC?

And am I right in assuming there will be a simple "render it whizzy fast in the cloud" button below the "open octane render viewport" button in 3ds Max?

maaan ))) if your machine can render 1000 frames in 10 hours then render them on your machine looool
for example mine with same Octane bench using 2 titans renders one frame in 20 minutes ((( so itsa 20000 minutes of render and that is unacceptable

[Rik]

Ha, I suppose it all depends on what you're rendering and the quality Mr Customer will settle for?
Mine was an exterior scene rendered at 1920x1080 and just using ambient occlusion for the global illumination.

around 30 seconds to render

It' wasn't the best in the world and I couldn't say it looked photoreal and there was a bit of noise and flickering but when you're in a rush...

My big hope was that ORC would improve the quality, not just the time, by enabling the use of more fancy colouring in techniques than ambient occlusion.

I'm now wondering if the new integrated denoise system (sadly not going to be released till after 3.0) will be the killer feature to persuade people to stay with Octane rather than jump ship to Redshift, Arion etc.

[Notiusweb]

Hi Goldorak, are the GPUs back at the farm air cooled or watercooled? And are they some special industrial strength GPU that is less subject to hardware crashing? I'm imagining one GPU in the ORC might fail while we are all burning them with our animations