S3D V4 takes FOREVER to save my gcode file

[cybrsage]

It literally takes 3 or 4 minutes to save a 30GB Gcode file created in S3D V4. Both the program and the save location are located on the same SSD. Yes, an SSD, a Samsung 850 EVO drive. It is super fast for everything else, and TRIM is run regularly, so I am at a loss.

It takes so long the program says (Not Responding)...but if I wait, the save completes and it responds again like normal.

Any ideas?

[brian442]

Well if it's a 30GB gcode file, I would expect it to take a long time to export! That's huge!

[cybrsage]

Why? It already processed it, which takes about 39 seconds to finish. Why would saving the already created file take so long?

[MasterFX]

Well I don't know how you get a 30 GB gcode file. Since most 3D-Printers can only handle FAT32 file systems, you will not be able to print or even save it to your SD-Card (since FAT32 only handles max. 4 GB files).

However, if the gcode file generation is as fast as you SSD is (lets say about 450 MB/s) then it will take at least one minute. But since I don't think that the file is written perfectly sequencial in > 128 KB blocks, 3 minutes is okay and not alarming slow.

[NitroXpress]

Same behavior here, and also with smaller GCode Files.
The problem has occured since V3.1.1
V 3.1.0 works super fast with same .stl files and heavy scripting !

Once again, I am very disappointed about the S3D Upgrade...

Frank

[arhi]

afaik s3d is executing the postprocessing script while saving... what do you have in your postprocessing script box?

[NitroXpress]

Strips,
Deletes,
Replaces.

For Perl a child's play...

[upsm]

For Perl a child's play...

30GB text file, both perl, awk and sed will have a field day with them
it's simple code to write, not quick code to execute

[NitroXpress]

For Perl a child's play...

30GB text file, both perl, awk and sed will have a field day with them
it's simple code to write, not quick code to execute

Ich have not spoken about 30GB text file...

[MasterFX]

For Perl a child's play...

30GB text file, both perl, awk and sed will have a field day with them
it's simple code to write, not quick code to execute

Ich have not spoken about 30GB text file...

Well, Postprocessing is applied to the gcode, not to the STL. And G-Code basically only a text-file.

However, I just took a look at the performance monitor when I saving a 200 MB Gcode, and it is only writing with approx 10 MB/s peak with a lot of pauses. My SSD is an Intel P3600 which can write easily 1 GB/s. And all my post processing is empty..
So something is wrong here. It is a little bit strange, because the gcode preview is based on an already generated g-code without the post processing. So it just has to be written to the drive.