• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EST 02:24
CET 08:24
KST 16:24
  • Home
  • Forum
  • Calendar
  • Streams
  • Liquipedia
  • Features
  • Store
  • EPT
  • TL+
  • StarCraft 2
  • Brood War
  • Smash
  • Heroes
  • Counter-Strike
  • Overwatch
  • Liquibet
  • Fantasy StarCraft
  • TLPD
  • StarCraft 2
  • Brood War
  • Blogs
Forum Sidebar
Events/Features
News
Featured News
Team Liquid Map Contest #2312[ASL22] Finals Preview: Sweet Victory!12[ASL22] Ro4 Preview: Mirror Mirror6[ASL22] Ro8 Preview: Within Reach5[ASL22] Ro8 Preview: In A Tizzy11
Community News
Weekly Cups (Nov 9-15): Clem and herO take over5Dark completes military service, returns to SC217[BSL23] RO16 Group Stage20Weekly Cups (Nov 2-8): herO back on top?2Weekly Cups (Oct 26 - Nov 1): MaxPax, herO, Solar win0
StarCraft 2
General
Team Liquid Map Contest #23 StarCraft open world shooter announced at BlizzCon Weekly Cups (Nov 9-15): Clem and herO take over No more SC2 streamers on team liquid? Dark completes military service, returns to SC2
Tourneys
soO & FanTaSy return! SC2 Kevin Scrim 4v4 (Nov 16) Sparkling Tuna Cup - Weekly Open Tournament RSL goes to London! 2026 Offline Finals Nov 21-22 Sea Duckling Open (Global, Bronze-Diamond) Dark returns! GSL CK #7 4v4 Team Battle (Nov 19)
Strategy
[H] ZvP Mid-Late Game: Stalkers Collossi HT
Custom Maps
[G] How to playtest arcade maps Starcraft 2 Advance [D] the control group Simple Questions/Answers
External Content
Mutation # 552 Secret Storm The PondCast: SC2 News & Results Mutation # 551 Robotic Revival Mutation # 550 Graveyard Shift
Brood War
General
Light introduces ShieldBattery on his YouTube List of top players active on ShieldBattery BW General Discussion BGH Auto Balance -> http://bghmmr.eu/ NaDa's Body
Tourneys
SC1 Kevin Scrim hosted by SOOP (Nov 18-19) KCM Race Survival 2026 Season 4 [Megathread] Daily Proleagues [BSL23] Ro16 Group D - Sunday 21:00 CET
Strategy
Pluto's TvP 5Marine 2Medic Push Simple Questions, Simple Answers Infested Terran strategies in 2026 Nuke strategy worked in K-League 2026-11-09
Other Games
General Games
Stormgate/Frost Giant Megathread The PlayStation 5 Warcraft III: The Frozen Throne Nintendo Switch Thread Free Space RTS Game, optimised f. Phone/Tablet etc
Dota 2
League of Legends
[TL LoL EUW IHs] Teemo shall perish
Heroes of the Storm
Heroes of the Storm 2.0
Hearthstone
Deck construction bug
TL Mafia
TL Mafia Community Thread
Community
General
US Politics Mega-thread Russo-Ukrainian War Thread Artificial Intelligence Thread The Big Programming Thread Trading/Investing Thread
Fan Clubs
Fan Club Resource Thread Reynor Fan Club The Flash Fan Club
Media & Entertainment
Movie Discussion! Anime Discussion Thread [Manga] One Piece
Sports
Football (Soccer) Thread TeamLiquid Health and Fitness Initiative For 2023
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Recent Gifted Posts
Blogs
The time I organised my…
AssyrianKing
Why I built Repalyzer (1.1.…
BlueStar
Innovate or Game Over?
TrAiDoS
ShieldBattery on Mac
Kraekkling
Can Bots Beat Pros?? Starcr…
namkraft
James Bond movies ranking - pa…
Topin
StarCraft improvement
iopq
Customize Sidebar...

Website Feedback

Closed Threads



Active: 23389 users

Minerals: An experimental approach to saturation.

Forum Index > SC2 General
Post a Reply
1 2 Next All
Cheticus
Profile Joined May 2010
United States83 Posts
Last Edited: 2010-06-03 01:38:02
June 03 2010 01:32 GMT
#1
Hi TL, this is my first post to the forums. I'm an old-time noncompetitive SC1 player who has been actively following SC2. I often see people discussing the ideal saturation points of mineral lines. It's common knowledge that you want at least two workers per mineral patch, and no more than three workers than mineral patch unless you're planning on transferring soon or using workers for other things in a crisis (bring extra SCVs on your thor push :D ).

Anyway, I've done some experimental testing of worker saturation for (assuming 8 mineral patches) 1 through 24 probes mining, and compiled the results in a little report that took about two or three hours to get together (keeping myself sharp for report-writing and uncertainty analysis). I used qxc's build tester map (which is awesome, thanks qxc!) and protoss for all tests. There's a TL;DR at the end, and pretty graphs. The curve fits are just that: curve fits to experimental data. Take them with a grain of salt. I probably kept one too many significant decimal points which are not really significant due to time and mineral resolutions.

In general the takeaways are:
Avoid having three workers per mineral patch until you have two workers at each mineral patch. If you have a patch with three miners and others with one miner (which is possible!), that mineral patch will quickly deplete relative to the other patches, causing an oversaturation of the other mineral patches leading to wasted worker efficiency. After two workers per mineral patch, each additional worker suffers significant diminishing returns in the relative increase in the next worker. Saturation really pays off when you're planning on expanding, since your expansion and main will then drop off into the linear region of worker income efficiency and you can just build workers from there.

No groundbreaking revolutions; just an additional source of information for people to look at if they're curious of one set of experimental results to try to quantify worker efficiency. It's evident though at higher numbers of saturation, the AI can have trouble finding minerals and oversaturation may even be a bit detrimental at exceedingly high numbers.

Anyways: The paper (it's not that long; you can skip to graphs and tl;dr at end!) I prepared is here: http://docs.google.com/fileview?id=0B3X9N0NR7fRtYzAzN2RlZTAtZDlkNS00M2Y2LTlkMGQtZGZkM2M5ZTA4Mjc0&hl=en

I don't know if google-docs has a bandwith limit or if anyone is even interested, but hopefully this can help someone curious about the results.

Also, here's a graph that you can find better explained in the report:
[image loading]

PS. I know there's at least one spelling or grammar error, the focus is the content and data analysis. Also, the (95%) thing next to the calibration means 'to 95% confidence on a student's t distribution'. I'm not a statistician, just an engineering u-grad with a small uncertainty bkg.

<3
muta_micro
Profile Joined February 2010
United States183 Posts
June 03 2010 01:38 GMT
#2
excellent contribution, most peoples first post isn't of this quality.
You know when you see a planet and you see that light, that planet isn't even there thats just a light, that's just your neighbor shining a flashlight into your backyard looking for coons.
Shizuru~
Profile Blog Joined April 2009
Malaysia1676 Posts
June 03 2010 02:27 GMT
#3
impressive efforts in the write-ups...

but i find your conclusions to be lacking or the amount of datas u've gathered, until we reach 2 per mineral patch saturations the mineral gathering rate pretty much goes up linearly from the data's u've presented, but i think what's actually important to know about is how much increase in mineral gathering rate on the 17th probe onwards, in fact would've been alot more helpful if u've calculated the gradient of the graph u've presented, one for the linear line for the first 16th probe and then for the line of sub-sequent probe until maximum saturation is reached...

NeoLearner
Profile Blog Joined January 2010
Belgium1847 Posts
June 03 2010 06:42 GMT
#4
Alright, a LaTeX paper on mining efficiency, been waiting for this. Great work!

From your raw data, would it be possible to calculate how much the "pay-off" time would increase for saturation higher than 2/minerals? Because that would be useful to know when trying to do a timing push.

So, when mining 3 drones/patch, some fumble and some stay cool? Any idea if this is correlated to patch distance? If it is, optimal could be ~ 20. 2 on each patch and 3 on the non-fumbling patches.

Now I build 16 + a few (3-4) spare ones which can be used to build defense or tech without giving up linear saturation.
Bankai - Correlation does not imply causation
artanis2
Profile Joined April 2010
United States732 Posts
Last Edited: 2010-06-03 08:08:31
June 03 2010 08:07 GMT
#5
Shizuru, look at the graph? Eyeballing it makes me think that the last 8 bring in half the increase that each of the first 16 did.
Infenwe
Profile Joined September 2009
Denmark170 Posts
June 03 2010 08:39 GMT
#6
Nice graphs. It's always good to have one's intuition confirmed by actual tests. I presume you made the graphs with gnuplot?

Now for some aesthetic comments:
A) Is that \documentclass[a4wide]{article} with \linespread{1.3} [1]? I thought lshort.pdf discouraged making the margins smaller because it reduces readability.
B) In Equation 1 I'd use \cdot instead of *.

[1]: It saddens me a bit that I can actually make an educated guess about things like this.
close the world - txen eht nepo
Endymion
Profile Blog Joined November 2009
United States3701 Posts
June 03 2010 08:45 GMT
#7
Impressive, thanks for the information! I'll have to seriously change my drone production now that I've seen this.
Have you considered the MMO-Champion forum? You are just as irrational and delusional with the right portion of nostalgic populism. By the way: The old Brood War was absolutely unplayable
igotmyown
Profile Blog Joined April 2009
United States4291 Posts
June 03 2010 09:01 GMT
#8
I read the document, and I understand that using an averaging approach it won't answer the following question directly.

But since you pointed out not to do 3 workers on a patch if there is a patch with 1 worker, is it ever better to put 2 workers on a (perhaps closer) patch than to put 1 worker on a farther patch?
afirlortwo
Profile Joined April 2010
United States161 Posts
June 03 2010 09:13 GMT
#9
nice work!
Just a momentary diversion on the road to the grave
drag_
Profile Blog Joined April 2010
England425 Posts
June 03 2010 09:16 GMT
#10
Really interesting read!
LordOFswe
Profile Joined April 2010
Sweden27 Posts
June 03 2010 09:58 GMT
#11
Good Job,
I did a similar work earlier (sorry did not publish it because i sort of forgot about it) and got a similar result, how ever i recalculated the result to mining/min*#probes*Mineral patch (that is according to if you have 1, 2, 3 or more probes /mineral patch) and got the following result:
[image loading]

I'm sorry i didn't have the time to correct the graphs so they had the same time spawn, but i hope you will get the big picture anyway.

The tests was also done with Protoss but on blistering sand against computer, and the time for each set of workers was at least 100sec and the times was started after the workers had been split.

the first graph shows the mean income / sec when you have 1,2,3,4,5 and 6 workers/mineral patch, and as it was tested with the standard 8 patches the unit count is 8,16,24,32,40,48.

at 1 probe /patch it will harvest 42 mineral/min and probe (335 minerals total/min) 100% of M.cap.*
at 2 probe /patch it will harvest 40 mineral/min and probe (639 minerals total/min) 95% of M.cap.*
at 3 probe /patch it will harvest 33 mineral/min and probe (791 minerals total/min) 79% of M.cap.*
at 4 probe /patch it will harvest 25 mineral/min and probe (811 minerals total/min) 60% of M.cap.*
at 5 probe /patch it will harvest 21 mineral/min and probe (835 minerals total/min) 50% of M.cap.*
at 6 probe /patch it will harvest 18 mineral/min and probe (839 minerals total/min) 43% of M.cap.*

*M.cap. = % of maximum capacity
"well, at least it still looks cool when you do a nice split.", gobrin June 03 2010
Shizuru~
Profile Blog Joined April 2009
Malaysia1676 Posts
June 03 2010 13:13 GMT
#12
On June 03 2010 17:07 artanis2 wrote:
Shizuru, look at the graph? Eyeballing it makes me think that the last 8 bring in half the increase that each of the first 16 did.


beats the whole purpose of a technical paper if we have to approximate visually by the graph instead of getting a concrete value out of it don't you think?
iSTime
Profile Joined November 2006
1579 Posts
June 03 2010 14:01 GMT
#13
What exactly is the point of the curve fitting? I mean, we already know from the other 20 threads on the topic that the last 8 workers are far less efficient than the first 16. What's special about the last 8 being fit by a cubic?
www.infinityseven.net
michaelhasanalias
Profile Joined May 2010
Korea (South)1231 Posts
June 03 2010 14:09 GMT
#14
Thank you very much for your article. It's not tremendously enlightening (and it shouldn't be), but there is a real gem in having most people's suspicions corroborated by hard data.

I hope you'll produce more in the future!
KR NsPMichael.805 | AM Michael.2640 | SEA Michael.523 | 엔에스피 New Star Players
Makh
Profile Joined June 2010
Canada143 Posts
June 03 2010 14:24 GMT
#15
Could you elaborate on your point regarding avoiding 3 harvesters per node where others have only 1? I imagine that the AI would motivate harvesters to end up at empty nodes rather than waiting for the assigned node to open up.
SC2 Instructional Audio Commentaries @ http://www.youtube.com/user/MakhStarcraft
Cheticus
Profile Joined May 2010
United States83 Posts
Last Edited: 2010-06-03 17:21:17
June 03 2010 17:19 GMT
#16
On June 03 2010 23:01 PJA wrote:
What exactly is the point of the curve fitting? I mean, we already know from the other 20 threads on the topic that the last 8 workers are far less efficient than the first 16. What's special about the last 8 being fit by a cubic?


The point of the curve fitting for the first set of workers (linear region) was to give a concrete experimental calibration to what we already know (and even a little bit of uncertainty to show what we don't know!). The cubic fit is just if you wanted to look at the relative difference between the linear region of worker efficiency compared to the 2-3/patch region. Looking at the difference between the two fits is an interesting thing also if anyone was interested, since that shows what you're trading off by saturating instead of having an expansion and main in the linear region (but I didn't do it). Nothing special at all whatsoever about a cubic. It just fits the data nicely and can model the results. I literally just noticed an inflection point and said: "Well it's not linear, it's not parabolic. Aha, look at that. Mmph. Cubic fit look good. Ungh. Cubic!"

Infenwe; I'm newer to LaTeX, and the fact that I put it in this form is basically just because I'm trying to get myself used to it. I'll be sure to take your advice when making papers for school and read over lshort (I just skimmed it originally) :D.

igotmyown: That's an interesting question. Reasonably it seems like 2 on a closer patch would be better when you're starting off in workers. I think that's probably the case. Again, I completely neglected the tiny differences between near and far mineral patches for the first 16 workers by averaging and just saying "aha, it looks linear as expected". In reality there's probably little ways like this to sneak an extra 20 or 25 minerals out while you're in the early stages of the game by choosing carefully and doing different subtle things with workers that ordinarily might be standing around for a few secs between buildings or what have you. Hell, that might even be the difference between a stalker and a zealot earlier on. I haven't collected any data on it though.

LordOFswe: Similar results are good, and lends to the idea that we're both on the right track, as well as the community of starcraft players in general; which is good. Your graphs show how additional workers beyond 3 per patch DO increase mineral yield over a given time (if only slightly), which I completely didn't consider looking at. All the more reason to never stop producing workers (especially when looking at transferring!).

Makh: Yeah. Try it yourself, or look at a replay from a recent game and you might be able to see it. I think the best way to do it is to get all patches having two workers/patch except for one patch with one worker on it. Rally your nexus/hatch/cc to a mineral patch with two workers and watch closely. If it doesn't work the first time, try it one or two more times and you'll probably see it (I did at least); three workers will contently mine from one mineral patch WITHOUT SEARCHING for an additional patch to mine from. It's like they'll each delay mining and just sit there in queue to mine from it. More often though yes, the AI will likely try to find an empty node. Maybe it's just the conditions under which I watched the probes, but I'm relatively certain I've seen it during normal ladder games (as I go watch a replay with my curiosity piqued to make sure).

also; thanks everyone for positive comments <3
Bob300
Profile Joined April 2010
United States505 Posts
June 03 2010 17:31 GMT
#17
WOW very nice job, happy that you did this.
NYC Suburbs --- College Freshman --- Season 1 - Drone Whiskey
LordOFswe
Profile Joined April 2010
Sweden27 Posts
June 03 2010 17:48 GMT
#18
On June 04 2010 02:19 Cheticus wrote:
Your graphs show how additional workers beyond 3 per patch DO increase mineral yield over a given time (if only slightly), which I completely didn't consider looking at. All the more reason to never stop producing workers (especially when looking at transferring!).


Hmmmm, well i would say that it proves that you DON'T want more then 3 workers/patch, as if you look on the extra mineral you got, that is an increase of 50 minerals/min if you double the amount of workers from 3/patch to 6/patch, on 8 patches it is 24 workers and as they 24 workers will earn you an additional 50 minerals/min it will take them 24 minutes to pay for them self. And if you go from 3/patch to 4/patch the extra probes will earn you one single extra mineral per minute and patch (3x33=99 and 4x25=100).
So you should only produce workers over 3/patch if you are planing for an expansion.
"well, at least it still looks cool when you do a nice split.", gobrin June 03 2010
darmousseh
Profile Blog Joined May 2010
United States3437 Posts
June 03 2010 19:37 GMT
#19
On June 04 2010 02:48 LordOFswe wrote:
Show nested quote +
On June 04 2010 02:19 Cheticus wrote:
Your graphs show how additional workers beyond 3 per patch DO increase mineral yield over a given time (if only slightly), which I completely didn't consider looking at. All the more reason to never stop producing workers (especially when looking at transferring!).


Hmmmm, well i would say that it proves that you DON'T want more then 3 workers/patch, as if you look on the extra mineral you got, that is an increase of 50 minerals/min if you double the amount of workers from 3/patch to 6/patch, on 8 patches it is 24 workers and as they 24 workers will earn you an additional 50 minerals/min it will take them 24 minutes to pay for them self. And if you go from 3/patch to 4/patch the extra probes will earn you one single extra mineral per minute and patch (3x33=99 and 4x25=100).
So you should only produce workers over 3/patch if you are planing for an expansion.



I would even think that you probably shouldn't build any extra workers until you begin the expansion. Then build like 4 workers while the expansion is going up take another 8 probes to the expansion to start with about 12 probes at expansion then start macroing up again. It seems like it would be better to have spent those minerals on extra units
Developer for http://mtgfiddle.com
Piousflea
Profile Joined February 2010
United States259 Posts
Last Edited: 2010-06-03 22:42:36
June 03 2010 21:54 GMT
#20
What matters to a real game is the incremental income per worker. If the first probe harvests 40 minerals/min, how many do you get from probe #17, 18, etc?

As far as the paper goes, your curve fittings make no sense. The linear portion of the curve has a non-zero intercept. At 0 workers you lose minerals, and the 1st worker is less effective than the 2nd worker. The cubic (why cubic?) portion of the curve eventually turns downward, meaning that if you extrapolate to 100 workers, you again lose minerals. You can use a spreadsheet to fit any curve to any data set. It's only a valid technique if your curve has some basis in reality.

The most mathematically sound approach is to use intercepts and asymptotes that make logical sense. That is, you need a curve that starts at 0 income for 0 workers and eventually levels off at a fixed income with infinite workers.

One logical approach would be a two-part linear-hyperbolic curve:
W<16: I = a*W
W>=16: I = (b * W) / (c + W)

This function starts at 0, and trends toward b as W goes to infinity. You could use a more sophisticated curve such as a logistic function for W>=16, but it would be a similar concept.

Ideally, you would also want to constrain the second curve to keep a smooth slope.
Seek, behold, and reveal the truth
1 2 Next All
Please log in or register to reply.
Live Events Refresh
Next event in 2h 37m
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
ProTech136
StarCraft: Brood War
Zeus 104
Shine 49
Larva 45
ToSsGirL 14
ajuk12(nOOB) 13
Force[name] 6
Other Games
summit1g8064
Coldzera 746
WinterStarcraft408
JimRising 381
Happy252
Mew2King83
Trikslyr19
[ Show 13 non-featured ]
StarCraft 2
• practicex 31
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• iopq 1
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• lizZardDota2351
League of Legends
• Rush1111
• Lourlo718
Upcoming Events
KCM Race Survival
2h 37m
Ultimate Battle
4h 37m
ZerO vs Bisu
Big Brain Bouts
9h 37m
FoxeR vs Bly
LetaleX vs MilkiCow
Reynor vs Lambo
RSL Revival
1d 3h
AI Arena Tournament
1d 9h
BSL
1d 12h
eOnzErG vs StRyKeR
Cross vs JDConan
RSL Revival
2 days
IPSL
2 days
Ret vs ggnore13
nOmaD vs Aether
BSL
2 days
Bonyth vs Doodle
Kyrie vs Jimin
Replay Cast
2 days
[ Show More ]
WardiTV Weekly
3 days
Kung Fu Cup
4 days
Solar vs Classic
ByuN vs SHIN
PiGosaur Cup
4 days
The PondCast
6 days
Liquipedia Results

Completed

Proleague 2026-11-17
Blizzard Classic Cup 2026
HCC Season 3

Ongoing

Acropolis #5
KCM Race Survival 2026 Season 4
International ShieldBattery League
BSL Season 23
IPSL Winter 2026-27
Calamity Cup Div. A Season 8
Underdog Cup 2026 Div 2-3
Stake Ranked Episode 6
BLAST Rivals Fall 2026
IEM Beijing 2026
PGL Masters Bucharest 2026
Stake Ranked Episode 5
1win Private Club #2
Thunderpick World Champ. '26
ESL Pro League Season 24
Stake Ranked Episode 4
1win Private Club #1
Logitech G Play Connect 2026
SL StarSeries Fall 2026
FISSURE Playground #3

Upcoming

Sector 591
YSL S4
SC4ALL II: Brood War
NBSL 2026 Xiamen LAN
BSL 23: Non-Korean Championship
HSC XXX
Stellar Fest 2: Lunar Cup
StarCraft2 Weekly Open Tournament 2026 Grand Finals
SC4ALL II: StarCraft II
Kung Fu Cup 2026 Grand Finals
RSL Offline Finals
IEM Kraków 2027
PGL Bucharest 2027
BLAST Bounty Winter 2027
PGL Major Singapore 2026
TLPD

1. ByuN
2. TY
3. Dark
4. Solar
5. Stats
6. Nerchio
7. sOs
8. soO
9. INnoVation
10. Elazer
1. Rain
2. Flash
3. EffOrt
4. Last
5. Bisu
6. Soulkey
7. Mini
8. Sharp
Sidebar Settings...

Advertising | Privacy Policy | Terms Of Use | Contact Us

Original banner artwork: Jim Warren
The contents of this webpage are copyright © 2026 TLnet. All Rights Reserved.