Return to Question

Because recently I've got an access to high-performance PC, I wanted to check on it capability of Blender fluid dynamics. First, I set simple system of fluid domain, fluid inflow etc etc, with Resolution Final:200, time from 0.000 to 4.000 and 1000 frames of animation. Blender told me that it will get 770 Mb of space. Great. After this, I made a script to run by ssh:

import bpy
bpy.ops.fluid.bake()
bpy.ops.render.render(animation=True)

and I run a command:

nohup ./blender -b ../u3.blend --python script.py &

AFTER 48 HOURS OF COMPUTING, THE FINAL TMP FOLDER LOOKED LIKE THIS:

179G    /tmp/blender_lFkZps/

Animation looked great, though - below I present single frame:

But still, I need answers!

1. Why the /tmp/blender_*** took so much space?
2. Why, even if fluid simulation had only 4 seconds - which gives 4*24=96 frames - it lasts for all 1000 frames? Does it mean that if I would change setting to 2000 frames it would be 2x slower?

Recently, I've received access to a high-performance PC; I wanted to check on its capability with Blender's fluid dynamics. First, I set simple system of fluid domain, fluid inflow, etc., with Final Resolution: 200, time from 0.000 to 4.000, and 1000 frames of animation. Blender told me, that it will get 770 Mb of space. After this, I made a script to run by the CLI through SSH:

import bpy
bpy.ops.fluid.bake()
bpy.ops.render.render(animation=True)

Then I ran a command:

nohup ./blender -b ../u3.blend --python script.py &

After 48 hours of computing, I received this from my tmp folder:

179G    /tmp/blender_lFkZps/

Animation looked great, though - below I present single frame:

Now for the questions.

1. Why the /tmp/blender_*** took so much space?
2. Why, even if fluid simulation had only 4 seconds - which gives 4*24=96 frames - it lasts for all 1000 frames? Does it mean that if I would change setting to 2000 frames it would be 2x slower?

Because recently I've got an access to high-performance PC, I wanted to check on it capability of Blender fluid dynamics. First, I set simple system of fluid domain, fluid inflow etc etc, with Resolution Final:200, time from 0.000 to 4.000 and 1000 frames of animation. Blender told me, that it will get 770 Mb of space. Great. After this, I made a script to run by ssh:

import bpy
bpy.ops.fluid.bake()
bpy.ops.render.render(animation=True)

and I run a command:

nohup ./blender -b ../u3.blend --python script.py &

AFTER 48 HOURS OF COMPUTING, THE FINAL TMP FOLDER LOOKED LIKE THIS:

179G    /tmp/blender_lFkZps/

Animation looked great, though - below I present single frame:

But still, I need answers!

1. Why the /tmp/blender_*** took so much space?
2. Why, even if fluid simulation had only 4 seconds - which gives 4*24=96 frames - it lasts for all 1000 frames? Does it mean that if I would change setting to 2000 frames it would be 2x slower?

Because recently I've got an access to high-performance PC, I wanted to check on it capability of Blender fluid dynamics. First, I set simple system of fluid domain, fluid inflow etc etc, with Resolution Final:200, time from 0.000 to 4.000 and 1000 frames of animation. Blender told me that it will get 770 Mb of space. Great. After this, I made a script to run by ssh:

import bpy
bpy.ops.fluid.bake()
bpy.ops.render.render(animation=True)

and I run a command:

nohup ./blender -b ../u3.blend --python script.py &

AFTER 48 HOURS OF COMPUTING, THE FINAL TMP FOLDER LOOKED LIKE THIS:

179G    /tmp/blender_lFkZps/

Animation looked great, though - below I present single frame:

But still, I need answers!

1. Why the /tmp/blender_*** took so much space?
2. Why, even if fluid simulation had only 4 seconds - which gives 4*24=96 frames - it lasts for all 1000 frames? Does it mean that if I would change setting to 2000 frames it would be 2x slower?

Because recently I've got an access to calculation PC, I wanted to check on it capability of Blender fluid dynamics. First, I set simple system of fluid domain, fluid inflow etc etc, with Resolution Final:200, time from 0.000 to 4.000 and 1000 frames of animation. Blender told me, that it will get 770 Mb of space. Great. After this, I made a script to run by ssh:

import bpy
bpy.ops.fluid.bake()
bpy.ops.render.render(animation=True)

and I run a command:

nohup ./blender -b ../u3.blend --python script.py &

AFTER 48 HOURS OF COMPUTING, THE FINAL TMP FOLDER LOOKED LIKE THIS:

179G    /tmp/blender_lFkZps/

Animation looked great, though - below I present single frame:

But still, I need answers!

1. Why the /tmp/blender_*** took so much space?
2. Why, even if fluid simulation had only 4 seconds - which gives 4*24=96 frames - it lasts for all 1000 frames? Does it mean that if I would change setting to 2000 frames it would be 2x slower?

Because recently I've got an access to high-performance PC, I wanted to check on it capability of Blender fluid dynamics. First, I set simple system of fluid domain, fluid inflow etc etc, with Resolution Final:200, time from 0.000 to 4.000 and 1000 frames of animation. Blender told me, that it will get 770 Mb of space. Great. After this, I made a script to run by ssh:

import bpy
bpy.ops.fluid.bake()
bpy.ops.render.render(animation=True)

and I run a command:

nohup ./blender -b ../u3.blend --python script.py &

AFTER 48 HOURS OF COMPUTING, THE FINAL TMP FOLDER LOOKED LIKE THIS:

179G    /tmp/blender_lFkZps/

Animation looked great, though - below I present single frame:

But still, I need answers!

1. Why the /tmp/blender_*** took so much space?
2. Why, even if fluid simulation had only 4 seconds - which gives 4*24=96 frames - it lasts for all 1000 frames? Does it mean that if I would change setting to 2000 frames it would be 2x slower?