FH
Father Horton
Sat, Feb 18, 2023 8:46 PM
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
DP
Dan Perry
Sat, Feb 18, 2023 9:50 PM
This data won't help:
Rendered three blades and caps: 4:08.431
Rendered three blades: 5:57.070
Rendered three blades and caps: 5:10.688
Rendered one blade in 2.704
Rendered two blades in 1:27.904
Re-rendered two blades in 1:54.037
Rendered three blades in 5:47.710
With a fresh instance of OpenSCAD:
Rendered three blades in 5:21.736
This was run on a newer high end Windows laptop with plenty of cpu and
memory available, so performance shouldn't be so random.
Dan
On Sat, Feb 18, 2023 at 12:47 PM Father Horton fatherhorton@gmail.com
wrote:
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
This data won't help:
Rendered three blades and caps: 4:08.431
Rendered three blades: 5:57.070
Rendered three blades and caps: 5:10.688
Rendered one blade in 2.704
Rendered two blades in 1:27.904
Re-rendered two blades in 1:54.037
Rendered three blades in 5:47.710
With a fresh instance of OpenSCAD:
Rendered three blades in 5:21.736
This was run on a newer high end Windows laptop with plenty of cpu and
memory available, so performance shouldn't be so random.
Dan
On Sat, Feb 18, 2023 at 12:47 PM Father Horton <fatherhorton@gmail.com>
wrote:
> Code below. When I render just the blades (no caps), one blade renders in
> about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
> caps, one blade renders in 43 seconds, two blades render in 2:23, and three
> in 6:24. Not only does the time increase, but it seems to be doing so
> exponentially.
>
> Why does this happen? What can I do about it?
>
> include <BOSL2/std.scad>
>
> $fn = 120;
> rad = 25;
> blade_length = .5 * 2 * PI * rad / 3;
> blade_peak = 2;
> outer_points = 30;
> alt = 100;
> base_thickness = 7;
> top_thickness = 1;
> hole_r = 11;
>
> circumference = rad * 22 / 7 * 2;
> blade_angle = blade_length / circumference * 360;
>
> bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
> 180]);
>
> module blade(rot) {
> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
> 100) translate([0, rad]) polygon(bladepts);
> };
>
> module cap(thickness, hole = false) {
> difference() {
> cylinder(h = thickness, r = rad);
> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
> hole_r);
> };
> };
>
> blade(0); // render time 0:00:42.953
> blade(120); // 0:02:23.338
> blade(240); // 0:06:24.477
>
> cap(base_thickness, hole = true);
> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
FH
Father Horton
Sat, Feb 18, 2023 10:37 PM
Huh. I'm running it on an Intel Core i5-10200H CPU @ 2.40GHz, 2400 Mhz, 4
Core(s), 8 Logical Processor(s) with 16GB.
On Sat, Feb 18, 2023 at 3:51 PM Dan Perry dan.p3rry@gmail.com wrote:
This data won't help:
Rendered three blades and caps: 4:08.431
Rendered three blades: 5:57.070
Rendered three blades and caps: 5:10.688
Rendered one blade in 2.704
Rendered two blades in 1:27.904
Re-rendered two blades in 1:54.037
Rendered three blades in 5:47.710
With a fresh instance of OpenSCAD:
Rendered three blades in 5:21.736
This was run on a newer high end Windows laptop with plenty of cpu and
memory available, so performance shouldn't be so random.
Dan
On Sat, Feb 18, 2023 at 12:47 PM Father Horton fatherhorton@gmail.com
wrote:
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Huh. I'm running it on an Intel Core i5-10200H CPU @ 2.40GHz, 2400 Mhz, 4
Core(s), 8 Logical Processor(s) with 16GB.
On Sat, Feb 18, 2023 at 3:51 PM Dan Perry <dan.p3rry@gmail.com> wrote:
> This data won't help:
> Rendered three blades and caps: 4:08.431
> Rendered three blades: 5:57.070
> Rendered three blades and caps: 5:10.688
> Rendered one blade in 2.704
> Rendered two blades in 1:27.904
> Re-rendered two blades in 1:54.037
> Rendered three blades in 5:47.710
> With a fresh instance of OpenSCAD:
> Rendered three blades in 5:21.736
>
> This was run on a newer high end Windows laptop with plenty of cpu and
> memory available, so performance shouldn't be so random.
> Dan
>
>
> On Sat, Feb 18, 2023 at 12:47 PM Father Horton <fatherhorton@gmail.com>
> wrote:
>
>> Code below. When I render just the blades (no caps), one blade renders in
>> about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
>> caps, one blade renders in 43 seconds, two blades render in 2:23, and three
>> in 6:24. Not only does the time increase, but it seems to be doing so
>> exponentially.
>>
>> Why does this happen? What can I do about it?
>>
>> include <BOSL2/std.scad>
>>
>> $fn = 120;
>> rad = 25;
>> blade_length = .5 * 2 * PI * rad / 3;
>> blade_peak = 2;
>> outer_points = 30;
>> alt = 100;
>> base_thickness = 7;
>> top_thickness = 1;
>> hole_r = 11;
>>
>> circumference = rad * 22 / 7 * 2;
>> blade_angle = blade_length / circumference * 360;
>>
>> bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
>> 180]);
>>
>> module blade(rot) {
>> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
>> 100) translate([0, rad]) polygon(bladepts);
>> };
>>
>> module cap(thickness, hole = false) {
>> difference() {
>> cylinder(h = thickness, r = rad);
>> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
>> hole_r);
>> };
>> };
>>
>> blade(0); // render time 0:00:42.953
>> blade(120); // 0:02:23.338
>> blade(240); // 0:06:24.477
>>
>> cap(base_thickness, hole = true);
>> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
K
Ken
Sat, Feb 18, 2023 11:06 PM
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
Code below. When I render just the blades (no caps), one blade renders
in about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I
add the caps, one blade renders in 43 seconds, two blades render in
2:23, and three in 6:24. Not only does the time increase, but it seems
to be doing so exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright",
blade_peak, 180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices
= 100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1,
r = hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
> Code below. When I render just the blades (no caps), one blade renders
> in about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I
> add the caps, one blade renders in 43 seconds, two blades render in
> 2:23, and three in 6:24. Not only does the time increase, but it seems
> to be doing so exponentially.
>
> Why does this happen? What can I do about it?
>
> include <BOSL2/std.scad>
>
> $fn = 120;
> rad = 25;
> blade_length = .5 * 2 * PI * rad / 3;
> blade_peak = 2;
> outer_points = 30;
> alt = 100;
> base_thickness = 7;
> top_thickness = 1;
> hole_r = 11;
>
> circumference = rad * 22 / 7 * 2;
> blade_angle = blade_length / circumference * 360;
>
> bladepts = turtle(["arcright", rad, blade_angle, "arcright",
> blade_peak, 180]);
>
> module blade(rot) {
> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices
> = 100) translate([0, rad]) polygon(bladepts);
> };
>
> module cap(thickness, hole = false) {
> difference() {
> cylinder(h = thickness, r = rad);
> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1,
> r = hole_r);
> };
> };
>
> blade(0); // render time 0:00:42.953
> blade(120); // 0:02:23.338
> blade(240); // 0:06:24.477
>
> cap(base_thickness, hole = true);
> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email todiscuss-leave@lists.openscad.org
--
Cheers, Ken
bats059@gmail.com
https://vk7krj.com/running.html
https://sstv.vk7krj.com/all_bands.html
----------------------------------------
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
MM
Michael Möller
Sat, Feb 18, 2023 11:34 PM
Mine is even stranger (sorry if this just adds more noise). OpenSCAD 2021.01
blade(0) : < 1 sec
blade(120) : < 1 sec
blade(0) and blade(120) : 02:35
Msquare
On Sun, 19 Feb 2023 at 00:07, Ken bats059@gmail.com wrote:
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
Mine is even stranger (sorry if this just adds more noise). OpenSCAD 2021.01
blade(0) : < 1 sec
blade(120) : < 1 sec
blade(0) and blade(120) : 02:35
Msquare
On Sun, 19 Feb 2023 at 00:07, Ken <bats059@gmail.com> wrote:
> Just to muddy the waters a little, I tried this code on my old win 10
> machine-
> i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
> mine died (driving 3 monitors- you can never have too much screen real
> estate!).
>
> Openscad 2022.12.06.ci12950
>
> 3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
>
> Without caps- Total rendering time: 0:00:02.886
>
> which doesn't seem to make sense- but is quite repeatable.....
>
> On 2023-02-19 07:46, Father Horton wrote:
>
> Code below. When I render just the blades (no caps), one blade renders in
> about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
> caps, one blade renders in 43 seconds, two blades render in 2:23, and three
> in 6:24. Not only does the time increase, but it seems to be doing so
> exponentially.
>
> Why does this happen? What can I do about it?
>
> include <BOSL2/std.scad>
>
> $fn = 120;
> rad = 25;
> blade_length = .5 * 2 * PI * rad / 3;
> blade_peak = 2;
> outer_points = 30;
> alt = 100;
> base_thickness = 7;
> top_thickness = 1;
> hole_r = 11;
>
> circumference = rad * 22 / 7 * 2;
> blade_angle = blade_length / circumference * 360;
>
> bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
> 180]);
>
> module blade(rot) {
> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
> 100) translate([0, rad]) polygon(bladepts);
> };
>
> module cap(thickness, hole = false) {
> difference() {
> cylinder(h = thickness, r = rad);
> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
> hole_r);
> };
> };
>
> blade(0); // render time 0:00:42.953
> blade(120); // 0:02:23.338
> blade(240); // 0:06:24.477
>
> cap(base_thickness, hole = true);
> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
> --
> Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
> ----------------------------------------
> A baby can be defined as an ego with a noise at one end and a smell at the other.
> Our job as parents is to teach them to control all three.
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
DM
Daniel Miner
Sat, Feb 18, 2023 11:35 PM
3 blades, with or without caps renders (F5) in under 0.4 seconds for me.
Of course, F6 is MUCH slower: 3 blades with caps: Total rendering time:
0:02:25.973
Is the graphics card used in this calculation?
I'd guess the OpenSCAD version may be the biggest factor.
i7-9700k 4.6Ghz, 32Gb RAM, Nvidia RTX 3050
OpenSCAD 2022.11.18.ci12805
Father Horton, are you looking at F6 times or F5 times?
On Sat, Feb 18, 2023 at 5:07 PM Ken bats059@gmail.com wrote:
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
3 blades, with or without caps renders (F5) in under 0.4 seconds for me.
Of course, F6 is MUCH slower: 3 blades with caps: Total rendering time:
0:02:25.973
Is the graphics card used in this calculation?
I'd *guess* the OpenSCAD version may be the biggest factor.
i7-9700k 4.6Ghz, 32Gb RAM, Nvidia RTX 3050
OpenSCAD 2022.11.18.ci12805
Father Horton, are you looking at F6 times or F5 times?
On Sat, Feb 18, 2023 at 5:07 PM Ken <bats059@gmail.com> wrote:
> Just to muddy the waters a little, I tried this code on my old win 10
> machine-
> i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
> mine died (driving 3 monitors- you can never have too much screen real
> estate!).
>
> Openscad 2022.12.06.ci12950
>
> 3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
>
> Without caps- Total rendering time: 0:00:02.886
>
> which doesn't seem to make sense- but is quite repeatable.....
>
> On 2023-02-19 07:46, Father Horton wrote:
>
> Code below. When I render just the blades (no caps), one blade renders in
> about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
> caps, one blade renders in 43 seconds, two blades render in 2:23, and three
> in 6:24. Not only does the time increase, but it seems to be doing so
> exponentially.
>
> Why does this happen? What can I do about it?
>
> include <BOSL2/std.scad>
>
> $fn = 120;
> rad = 25;
> blade_length = .5 * 2 * PI * rad / 3;
> blade_peak = 2;
> outer_points = 30;
> alt = 100;
> base_thickness = 7;
> top_thickness = 1;
> hole_r = 11;
>
> circumference = rad * 22 / 7 * 2;
> blade_angle = blade_length / circumference * 360;
>
> bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
> 180]);
>
> module blade(rot) {
> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
> 100) translate([0, rad]) polygon(bladepts);
> };
>
> module cap(thickness, hole = false) {
> difference() {
> cylinder(h = thickness, r = rad);
> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
> hole_r);
> };
> };
>
> blade(0); // render time 0:00:42.953
> blade(120); // 0:02:23.338
> blade(240); // 0:06:24.477
>
> cap(base_thickness, hole = true);
> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
>
> --
> Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
> ----------------------------------------
> A baby can be defined as an ego with a noise at one end and a smell at the other.
> Our job as parents is to teach them to control all three.
>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
AM
Adrian Mariano
Sat, Feb 18, 2023 11:43 PM
For OpenSCAD, hitting F5 is "preview" and hitting F6 is "render". So if
something "renders" in 2 hours that means it was with F6.
Recent dev snapshots of OpenSCAD have rendering speedups that can make
renders 10x faster.
For time testing of renders you need to clear the cache after each test, or
you might be getting improper timing results based on having already stored
some geometry data in the cache.
On Sat, Feb 18, 2023 at 6:36 PM Michael Möller private2michael@gmail.com
wrote:
Mine is even stranger (sorry if this just adds more noise). OpenSCAD
2021.01
blade(0) : < 1 sec
blade(120) : < 1 sec
blade(0) and blade(120) : 02:35
Msquare
On Sun, 19 Feb 2023 at 00:07, Ken bats059@gmail.com wrote:
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
Code below. When I render just the blades (no caps), one blade renders in
about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
caps, one blade renders in 43 seconds, two blades render in 2:23, and three
in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
For OpenSCAD, hitting F5 is "preview" and hitting F6 is "render". So if
something "renders" in 2 hours that means it was with F6.
Recent dev snapshots of OpenSCAD have rendering speedups that can make
renders 10x faster.
For time testing of renders you need to clear the cache after each test, or
you might be getting improper timing results based on having already stored
some geometry data in the cache.
On Sat, Feb 18, 2023 at 6:36 PM Michael Möller <private2michael@gmail.com>
wrote:
> Mine is even stranger (sorry if this just adds more noise). OpenSCAD
> 2021.01
>
> blade(0) : < 1 sec
> blade(120) : < 1 sec
> blade(0) and blade(120) : 02:35
>
> Msquare
>
>
> On Sun, 19 Feb 2023 at 00:07, Ken <bats059@gmail.com> wrote:
>
>> Just to muddy the waters a little, I tried this code on my old win 10
>> machine-
>> i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
>> mine died (driving 3 monitors- you can never have too much screen real
>> estate!).
>>
>> Openscad 2022.12.06.ci12950
>>
>> 3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
>>
>> Without caps- Total rendering time: 0:00:02.886
>>
>> which doesn't seem to make sense- but is quite repeatable.....
>>
>> On 2023-02-19 07:46, Father Horton wrote:
>>
>> Code below. When I render just the blades (no caps), one blade renders in
>> about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add the
>> caps, one blade renders in 43 seconds, two blades render in 2:23, and three
>> in 6:24. Not only does the time increase, but it seems to be doing so
>> exponentially.
>>
>> Why does this happen? What can I do about it?
>>
>> include <BOSL2/std.scad>
>>
>> $fn = 120;
>> rad = 25;
>> blade_length = .5 * 2 * PI * rad / 3;
>> blade_peak = 2;
>> outer_points = 30;
>> alt = 100;
>> base_thickness = 7;
>> top_thickness = 1;
>> hole_r = 11;
>>
>> circumference = rad * 22 / 7 * 2;
>> blade_angle = blade_length / circumference * 360;
>>
>> bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
>> 180]);
>>
>> module blade(rot) {
>> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
>> 100) translate([0, rad]) polygon(bladepts);
>> };
>>
>> module cap(thickness, hole = false) {
>> difference() {
>> cylinder(h = thickness, r = rad);
>> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r =
>> hole_r);
>> };
>> };
>>
>> blade(0); // render time 0:00:42.953
>> blade(120); // 0:02:23.338
>> blade(240); // 0:06:24.477
>>
>> cap(base_thickness, hole = true);
>> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
>>
>> --
>> Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
>> ----------------------------------------
>> A baby can be defined as an ego with a noise at one end and a smell at the other.
>> Our job as parents is to teach them to control all three.
>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
DP
Dan Perry
Sun, Feb 19, 2023 12:17 AM
How does one clear the cache?
Dan
On Sat, Feb 18, 2023 at 3:44 PM Adrian Mariano avm4@cornell.edu wrote:
For OpenSCAD, hitting F5 is "preview" and hitting F6 is "render". So if
something "renders" in 2 hours that means it was with F6.
Recent dev snapshots of OpenSCAD have rendering speedups that can make
renders 10x faster.
For time testing of renders you need to clear the cache after each test,
or you might be getting improper timing results based on having already
stored some geometry data in the cache.
On Sat, Feb 18, 2023 at 6:36 PM Michael Möller private2michael@gmail.com
wrote:
Mine is even stranger (sorry if this just adds more noise). OpenSCAD
2021.01
blade(0) : < 1 sec
blade(120) : < 1 sec
blade(0) and blade(120) : 02:35
Msquare
On Sun, 19 Feb 2023 at 00:07, Ken bats059@gmail.com wrote:
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
Code below. When I render just the blades (no caps), one blade renders
in about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add
the caps, one blade renders in 43 seconds, two blades render in 2:23, and
three in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r
= hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
How does one clear the cache?
Dan
On Sat, Feb 18, 2023 at 3:44 PM Adrian Mariano <avm4@cornell.edu> wrote:
> For OpenSCAD, hitting F5 is "preview" and hitting F6 is "render". So if
> something "renders" in 2 hours that means it was with F6.
>
> Recent dev snapshots of OpenSCAD have rendering speedups that can make
> renders 10x faster.
>
> For time testing of renders you need to clear the cache after each test,
> or you might be getting improper timing results based on having already
> stored some geometry data in the cache.
>
>
> On Sat, Feb 18, 2023 at 6:36 PM Michael Möller <private2michael@gmail.com>
> wrote:
>
>> Mine is even stranger (sorry if this just adds more noise). OpenSCAD
>> 2021.01
>>
>> blade(0) : < 1 sec
>> blade(120) : < 1 sec
>> blade(0) and blade(120) : 02:35
>>
>> Msquare
>>
>>
>> On Sun, 19 Feb 2023 at 00:07, Ken <bats059@gmail.com> wrote:
>>
>>> Just to muddy the waters a little, I tried this code on my old win 10
>>> machine-
>>> i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
>>> mine died (driving 3 monitors- you can never have too much screen real
>>> estate!).
>>>
>>> Openscad 2022.12.06.ci12950
>>>
>>> 3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
>>>
>>> Without caps- Total rendering time: 0:00:02.886
>>>
>>> which doesn't seem to make sense- but is quite repeatable.....
>>>
>>> On 2023-02-19 07:46, Father Horton wrote:
>>>
>>> Code below. When I render just the blades (no caps), one blade renders
>>> in about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add
>>> the caps, one blade renders in 43 seconds, two blades render in 2:23, and
>>> three in 6:24. Not only does the time increase, but it seems to be doing so
>>> exponentially.
>>>
>>> Why does this happen? What can I do about it?
>>>
>>> include <BOSL2/std.scad>
>>>
>>> $fn = 120;
>>> rad = 25;
>>> blade_length = .5 * 2 * PI * rad / 3;
>>> blade_peak = 2;
>>> outer_points = 30;
>>> alt = 100;
>>> base_thickness = 7;
>>> top_thickness = 1;
>>> hole_r = 11;
>>>
>>> circumference = rad * 22 / 7 * 2;
>>> blade_angle = blade_length / circumference * 360;
>>>
>>> bladepts = turtle(["arcright", rad, blade_angle, "arcright", blade_peak,
>>> 180]);
>>>
>>> module blade(rot) {
>>> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices =
>>> 100) translate([0, rad]) polygon(bladepts);
>>> };
>>>
>>> module cap(thickness, hole = false) {
>>> difference() {
>>> cylinder(h = thickness, r = rad);
>>> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r
>>> = hole_r);
>>> };
>>> };
>>>
>>> blade(0); // render time 0:00:42.953
>>> blade(120); // 0:02:23.338
>>> blade(240); // 0:06:24.477
>>>
>>> cap(base_thickness, hole = true);
>>> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>>>
>>> _______________________________________________
>>> OpenSCAD mailing list
>>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>>
>>>
>>> --
>>> Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
>>> ----------------------------------------
>>> A baby can be defined as an ego with a noise at one end and a smell at the other.
>>> Our job as parents is to teach them to control all three.
>>>
>>> _______________________________________________
>>> OpenSCAD mailing list
>>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
NH
nop head
Sun, Feb 19, 2023 12:30 AM
The last entry on the Design menu tab.
On Sun, 19 Feb 2023 at 00:17, Dan Perry dan.p3rry@gmail.com wrote:
How does one clear the cache?
Dan
On Sat, Feb 18, 2023 at 3:44 PM Adrian Mariano avm4@cornell.edu wrote:
For OpenSCAD, hitting F5 is "preview" and hitting F6 is "render". So if
something "renders" in 2 hours that means it was with F6.
Recent dev snapshots of OpenSCAD have rendering speedups that can make
renders 10x faster.
For time testing of renders you need to clear the cache after each test,
or you might be getting improper timing results based on having already
stored some geometry data in the cache.
On Sat, Feb 18, 2023 at 6:36 PM Michael Möller private2michael@gmail.com
wrote:
Mine is even stranger (sorry if this just adds more noise). OpenSCAD
2021.01
blade(0) : < 1 sec
blade(120) : < 1 sec
blade(0) and blade(120) : 02:35
Msquare
On Sun, 19 Feb 2023 at 00:07, Ken bats059@gmail.com wrote:
Just to muddy the waters a little, I tried this code on my old win 10
machine-
i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
mine died (driving 3 monitors- you can never have too much screen real
estate!).
Openscad 2022.12.06.ci12950
3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
Without caps- Total rendering time: 0:00:02.886
which doesn't seem to make sense- but is quite repeatable.....
On 2023-02-19 07:46, Father Horton wrote:
Code below. When I render just the blades (no caps), one blade renders
in about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add
the caps, one blade renders in 43 seconds, two blades render in 2:23, and
three in 6:24. Not only does the time increase, but it seems to be doing so
exponentially.
Why does this happen? What can I do about it?
include <BOSL2/std.scad>
$fn = 120;
rad = 25;
blade_length = .5 * 2 * PI * rad / 3;
blade_peak = 2;
outer_points = 30;
alt = 100;
base_thickness = 7;
top_thickness = 1;
hole_r = 11;
circumference = rad * 22 / 7 * 2;
blade_angle = blade_length / circumference * 360;
bladepts = turtle(["arcright", rad, blade_angle, "arcright",
blade_peak, 180]);
module blade(rot) {
rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices
= 100) translate([0, rad]) polygon(bladepts);
};
module cap(thickness, hole = false) {
difference() {
cylinder(h = thickness, r = rad);
if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r
= hole_r);
};
};
blade(0); // render time 0:00:42.953
blade(120); // 0:02:23.338
blade(240); // 0:06:24.477
cap(base_thickness, hole = true);
translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
--
Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
A baby can be defined as an ego with a noise at one end and a smell at the other.
Our job as parents is to teach them to control all three.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
The last entry on the Design menu tab.
On Sun, 19 Feb 2023 at 00:17, Dan Perry <dan.p3rry@gmail.com> wrote:
> How does one clear the cache?
> Dan
>
>
> On Sat, Feb 18, 2023 at 3:44 PM Adrian Mariano <avm4@cornell.edu> wrote:
>
>> For OpenSCAD, hitting F5 is "preview" and hitting F6 is "render". So if
>> something "renders" in 2 hours that means it was with F6.
>>
>> Recent dev snapshots of OpenSCAD have rendering speedups that can make
>> renders 10x faster.
>>
>> For time testing of renders you need to clear the cache after each test,
>> or you might be getting improper timing results based on having already
>> stored some geometry data in the cache.
>>
>>
>> On Sat, Feb 18, 2023 at 6:36 PM Michael Möller <private2michael@gmail.com>
>> wrote:
>>
>>> Mine is even stranger (sorry if this just adds more noise). OpenSCAD
>>> 2021.01
>>>
>>> blade(0) : < 1 sec
>>> blade(120) : < 1 sec
>>> blade(0) and blade(120) : 02:35
>>>
>>> Msquare
>>>
>>>
>>> On Sun, 19 Feb 2023 at 00:07, Ken <bats059@gmail.com> wrote:
>>>
>>>> Just to muddy the waters a little, I tried this code on my old win 10
>>>> machine-
>>>> i7 64-bit, 3.4Ghz, 24G ram, video card rescued from the local tip after
>>>> mine died (driving 3 monitors- you can never have too much screen real
>>>> estate!).
>>>>
>>>> Openscad 2022.12.06.ci12950
>>>>
>>>> 3 blades plus top and bottom caps- Total rendering time: 0:00:00.618
>>>>
>>>> Without caps- Total rendering time: 0:00:02.886
>>>>
>>>> which doesn't seem to make sense- but is quite repeatable.....
>>>>
>>>> On 2023-02-19 07:46, Father Horton wrote:
>>>>
>>>> Code below. When I render just the blades (no caps), one blade renders
>>>> in about 4 seconds, two in 8 seconds, and 3 in 12, so linear. When I add
>>>> the caps, one blade renders in 43 seconds, two blades render in 2:23, and
>>>> three in 6:24. Not only does the time increase, but it seems to be doing so
>>>> exponentially.
>>>>
>>>> Why does this happen? What can I do about it?
>>>>
>>>> include <BOSL2/std.scad>
>>>>
>>>> $fn = 120;
>>>> rad = 25;
>>>> blade_length = .5 * 2 * PI * rad / 3;
>>>> blade_peak = 2;
>>>> outer_points = 30;
>>>> alt = 100;
>>>> base_thickness = 7;
>>>> top_thickness = 1;
>>>> hole_r = 11;
>>>>
>>>> circumference = rad * 22 / 7 * 2;
>>>> blade_angle = blade_length / circumference * 360;
>>>>
>>>> bladepts = turtle(["arcright", rad, blade_angle, "arcright",
>>>> blade_peak, 180]);
>>>>
>>>> module blade(rot) {
>>>> rotate([0, 0, rot]) linear_extrude(height = alt, twist=120, slices
>>>> = 100) translate([0, rad]) polygon(bladepts);
>>>> };
>>>>
>>>> module cap(thickness, hole = false) {
>>>> difference() {
>>>> cylinder(h = thickness, r = rad);
>>>> if (hole) translate([0, 0, -0.5]) cylinder(h = thickness + 1, r
>>>> = hole_r);
>>>> };
>>>> };
>>>>
>>>> blade(0); // render time 0:00:42.953
>>>> blade(120); // 0:02:23.338
>>>> blade(240); // 0:06:24.477
>>>>
>>>> cap(base_thickness, hole = true);
>>>> translate([0, 0, alt - top_thickness]) cap(top_thickness, hole = false);
>>>>
>>>> _______________________________________________
>>>> OpenSCAD mailing list
>>>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>>>
>>>>
>>>> --
>>>> Cheers, Kenbats059@gmail.comhttps://vk7krj.com/running.htmlhttps://sstv.vk7krj.com/all_bands.html
>>>> ----------------------------------------
>>>> A baby can be defined as an ego with a noise at one end and a smell at the other.
>>>> Our job as parents is to teach them to control all three.
>>>>
>>>> _______________________________________________
>>>> OpenSCAD mailing list
>>>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>>>
>>> _______________________________________________
>>> OpenSCAD mailing list
>>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>>
>> _______________________________________________
>> OpenSCAD mailing list
>> To unsubscribe send an email to discuss-leave@lists.openscad.org
>>
> _______________________________________________
> OpenSCAD mailing list
> To unsubscribe send an email to discuss-leave@lists.openscad.org
>
FH
Father Horton
Sun, Feb 19, 2023 2:19 AM
I downloaded and ran 2023.2.15, ran each one twice, and flushed the cache
between runs.
With caps:
1 blade: 0:21 both times
2 blades: 1:14 both times
3 blades: 3:11/3:18
With caps:
1 blade: 1.4 sec/.4 sec
2 blades: 1:07 both times
3 blades: 3:31/3:35
So the dev release does render faster, and I have no idea what effect the
caps are having. The exponential time increase makes sense if OpenSCAD is
having to check for collisions of more objects or something like that.
I downloaded and ran 2023.2.15, ran each one twice, and flushed the cache
between runs.
With caps:
1 blade: 0:21 both times
2 blades: 1:14 both times
3 blades: 3:11/3:18
With caps:
1 blade: 1.4 sec/.4 sec
2 blades: 1:07 both times
3 blades: 3:31/3:35
So the dev release does render faster, and I have no idea what effect the
caps are having. The exponential time increase makes sense if OpenSCAD is
having to check for collisions of more objects or something like that.
