Friday Facts #206 - Workflow optimisation

Regular reports on Factorio development.

luc
Fast Inserter
Fast Inserter
Posts: 170
Joined: Sun Jul 17, 2016 9:53 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by luc » Fri Sep 01, 2017 8:28 pm

kovarex wrote:soon
Can't wait :)

Edit: you're editing your post? So can I!

Will the replacement between belt and splitter also work with two belts? Since I'd use it most often when having a lot of belts next to each other, when doing some balancing between them.

kovarex
Factorio Staff
Factorio Staff
Posts: 7402
Joined: Wed Feb 06, 2013 12:00 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by kovarex » Fri Sep 01, 2017 8:32 pm

luc wrote:Will the replacement between belt and splitter also work with two belts?
Yes, it would be sad if it didn't :)

d.kr
Burner Inserter
Burner Inserter
Posts: 6
Joined: Wed Dec 24, 2014 1:04 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by d.kr » Fri Sep 01, 2017 8:35 pm

It turned out that it is most probably caused by slow SSD speed, which could be caused by writing a huge amount of data when working. From what I found on the internet, the typical SSD write capacity is something around 1TB of data, which is not so hard to approach if one recompilation cycle of Factorio generates 5GB of data.
Why are you compiling on a phyiscal disk and not a ram-disk? You might need more ram (but your beefy pc probably can handle that) but its faster and you only a few build artifacts of that data anyway.

Edit: Reading the everything before commenting might have helped:
and I'm planning to get enough memory to compile on ramdisk to prevent this problem in the future.
Last edited by d.kr on Sun Sep 03, 2017 9:59 am, edited 1 time in total.

Bilka
Factorio Staff
Factorio Staff
Posts: 2030
Joined: Sat Aug 13, 2016 9:20 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by Bilka » Fri Sep 01, 2017 8:36 pm

Nice new features! Some many QoL changes again :D
I'm an admin over at https://wiki.factorio.com. Feel free to contact me if there's anything wrong (or right) with it.

LD100
Burner Inserter
Burner Inserter
Posts: 14
Joined: Sun Jul 31, 2016 7:45 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by LD100 » Fri Sep 01, 2017 8:48 pm

The white poles at the top front of the pumpjack look wired shouldn't there be a rope and not a pole like in this video: https://youtu.be/GQJWcp8EcrE?t=13s


beiju
Inserter
Inserter
Posts: 35
Joined: Thu Feb 02, 2017 3:52 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by beiju » Fri Sep 01, 2017 8:53 pm

The belt fast-replace looks like it'll be great! While you're there, can you also make it so rotating a belt by fast replacement doesn't put its items in your inventory? You can already achieve that by using R with an empty cursor, so it should be possible, and it would eliminate the last common case for getting random extras in your inventory now that splitter and underground fast replacement doesn't do that.

meelock
Burner Inserter
Burner Inserter
Posts: 5
Joined: Wed Sep 23, 2015 5:06 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by meelock » Fri Sep 01, 2017 8:55 pm

The storage tank interior background really needs to be dark, otherwise, the fact that the interior isn't 3d is really glaring.

peet1993
Burner Inserter
Burner Inserter
Posts: 19
Joined: Fri Sep 01, 2017 8:46 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by peet1993 » Fri Sep 01, 2017 8:55 pm

d.kr wrote:
It turned out that it is most probably caused by slow SSD speed, which could be caused by writing a huge amount of data when working. From what I found on the internet, the typical SSD write capacity is something around 1TB of data, which is not so hard to approach if one recompilation cycle of Factorio generates 5GB of data.
Why are you compiling on a phyiscal disk and not a ram-disk? You might need more ram (but your beefy pc probably can handle that) but its faster and you only a few build artifacts of that data anyway.
He literally says that he will do so in the FFF :D
I want to add that a cheap SSD like the Samsung 750 Evo (using TLC memory) has a lifetime of 35TBWritten. I don't know where you got the 1TB value from, but i guess you got the lifetime of a single cell. This is enhanced by so-called wear leveling. Of course you can reach the TBW cap pretty fast aswell if you recompile often :D

Nice article, and say thanks to your new guy for this awesome QoL change!
Last edited by peet1993 on Fri Sep 01, 2017 8:58 pm, edited 1 time in total.

ohmusama
Inserter
Inserter
Posts: 27
Joined: Sat Jan 14, 2017 2:05 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by ohmusama » Fri Sep 01, 2017 8:56 pm

Formal Rice Farmer wrote:Image
Non joining pipes confirmed

kovarex
Factorio Staff
Factorio Staff
Posts: 7402
Joined: Wed Feb 06, 2013 12:00 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by kovarex » Fri Sep 01, 2017 8:59 pm

peet1993 wrote:I don't know where you got the 1TB value from, but i guess you got the lifetime of a single cell. This is enhanced by so-called wear leveling. But you can reach the TBW cap pretty fast aswell if you recompile often :D

Nice article, and say thanks to your new guy for this awesome QoL change!
Sorry, I meant 1000TB (I updated the post).

kovarex
Factorio Staff
Factorio Staff
Posts: 7402
Joined: Wed Feb 06, 2013 12:00 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by kovarex » Fri Sep 01, 2017 8:59 pm

ohmusama wrote:Non joining pipes confirmed
Things like that happen when the composition is created in the graphics editor, and not in the game.

peet1993
Burner Inserter
Burner Inserter
Posts: 19
Joined: Fri Sep 01, 2017 8:46 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by peet1993 » Fri Sep 01, 2017 9:02 pm

kovarex wrote:
peet1993 wrote:I don't know where you got the 1TB value from, but i guess you got the lifetime of a single cell. This is enhanced by so-called wear leveling. But you can reach the TBW cap pretty fast aswell if you recompile often :D

Nice article, and say thanks to your new guy for this awesome QoL change!
Sorry, I meant 1000TB (I updated the post).
Well I guess that makes my explanation obsolete :)
Last edited by peet1993 on Fri Sep 01, 2017 9:02 pm, edited 1 time in total.

PacifyerGrey
Smart Inserter
Smart Inserter
Posts: 1041
Joined: Wed Jun 29, 2016 10:02 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by PacifyerGrey » Fri Sep 01, 2017 9:02 pm

I am glad you found some time to make your own life easier.

I know compilation times just rob you of your time but they also give you some rest. And you just removed these 5 min breaks :) Now to get a break you will need to find another reason (hopefully not smoking).

I am really happy about belt/splitter replacements. Hopefully this will also work with blueprints (maybe in Shift [force] mode).

And yes SSD speed becomes lower when it is getting full. Especially if you have a lot of write operations while reaching max capacity.
So for dynamic data (like compilation) or databases it is best to use HDD (preferably SAS) in hardware RAID arrays (with a Strip in nature, RAID5 [fine] or RAID10 [best]). Such array will serve you for many years with near to no damage like SSD have. However this is far more expensive compared to common SSD drives.

And as always - love HR graphics. And waiting for 0.16 like there is no tomorrow.

I promise to make a set of cool video tutorials when it comes out.

User avatar
ledow
Long Handed Inserter
Long Handed Inserter
Posts: 86
Joined: Sat Sep 24, 2016 3:00 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by ledow » Fri Sep 01, 2017 9:04 pm

Where does the time spent on that compile optimisation appear on the classic XKCD chart?:

https://xkcd.com/1205/

And the more junk like boost that you throw in (and I imagine much of that is spent compiling code that's later discarded because it's not actually used) the worse it will be.

I'm more surprised you don't just have a cached/distributed compile and/or automatic compilation when a SCM update is pushed.

By the time you've pushed new code to a tree, and navigated to a shared drive of some type to run the new binary, it'll probably be ready.

BHakluyt
Fast Inserter
Fast Inserter
Posts: 171
Joined: Sat Oct 08, 2016 12:43 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by BHakluyt » Fri Sep 01, 2017 9:05 pm

The fast belt replacement looks fantastic. Can't wait for 0.16 for all the nice features and HR graphics. I hope with all your optimisations and speeding up processes that you have more time to make the spidertron. Keep up the great work and thank you all for one of the best games ever!

ohmusama
Inserter
Inserter
Posts: 27
Joined: Sat Jan 14, 2017 2:05 am
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by ohmusama » Fri Sep 01, 2017 9:08 pm

kovarex wrote:
ohmusama wrote:Non joining pipes confirmed
Things like that happen when the composition is created in the graphics editor, and not in the game.
Non joining pipes unconfirmed. :(

Although I could use to different kinds of pipes that don't connect (except to structures, like pumps, tanks, refineries, etc). Would be nice for a fluid bus.

User avatar
Tomik
Fast Inserter
Fast Inserter
Posts: 204
Joined: Mon Apr 18, 2016 3:30 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by Tomik » Fri Sep 01, 2017 9:13 pm

So Jai Programming Language? You mean this?

https://en.wikipedia.org/wiki/Jonathan_ ... I_language
Image

bman212121
Fast Inserter
Fast Inserter
Posts: 115
Joined: Mon Apr 18, 2016 8:08 pm
Contact:

Re: Friday Facts #206 - Workflow optimisation

Post by bman212121 » Fri Sep 01, 2017 9:14 pm

Of the XKCD posts I would have picked this one first:

https://xkcd.com/303/

Post Reply

Return to “News”

Who is online

Users browsing this forum: No registered users