|
|
Hi(gh)!
On 15.08.20 15:19, Bald Eagle wrote:
> =?UTF-8?Q?J=c3=b6rg_=22Yadgar=22_Bleimann?= <yaz### [at] gmxde> wrote:
>
>> Contrary to Bald Eagle's recommendations, precalculations and
>> concatenations of #write operations did not help much in increasing
>> parsing speed of the mesh2 generating script - calculating a mesh2 from
>> the n42e044 heightfield still took 2 hours, 32 minutes. I need a faster
>> computer! 16-core Ryzen Threadripper fitted with 128 GiB of RAM or
>> something like that...
>
> generating a 3601 by 3601 mesh took some cool 200 days! My version does it in
> two and a half hours...
>
> Trying to help here with some constructive criticism.
>
> Yadgar, I'm sorry, but something is _wrong_.
> 3601 x 3601 is only 12,967,201 pixels.
> In its simplest terms, you're taking those pixels, and instead of x, y, RGB
> you're writing some data to disk as x, y, (altitude).
> That should take _minutes_.
I can't write binary data to disk as I have to build a mesh2 object -
AFAIK this can only be achieved by writing ASCII text!
See you in Khyberspace!
Yadgar
Post a reply to this message
|
|