From 5226d620d0d80794efce995a6ac393cbcd88f049 Mon Sep 17 00:00:00 2001
From: David Anderson <davea@ssl.berkeley.edu>
Date: Sun, 21 Jun 2015 00:40:01 -0700
Subject: [PATCH] client: allow initial scheduler request to request N
 instances.

I made a change on 27 Feb 2009 that set the initial request to 0 instances.
I'm not sure what the rationale was - the checkin note didn't say.
---
 client/work_fetch.cpp | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/client/work_fetch.cpp b/client/work_fetch.cpp
index eb98c5f486..6f06c1ed50 100644
--- a/client/work_fetch.cpp
+++ b/client/work_fetch.cpp
@@ -906,8 +906,8 @@ void WORK_FETCH::handle_reply(
 }
 
 // set up for initial RPC.
-// arrange to always get one job, even if we don't need it or can't handle it.
-// (this is probably what user wants)
+// Ask for just 1 job per instance,
+// since we don't have good runtime estimates yet
 //
 void WORK_FETCH::set_initial_work_request(PROJECT* p) {
     for (int i=0; i<coprocs.n_rsc; i++) {
@@ -918,7 +918,6 @@ void WORK_FETCH::set_initial_work_request(PROJECT* p) {
                 rsc_work_fetch[i].req_secs = 0;
             }
         }
-        rsc_work_fetch[i].req_instances = 0;
         rsc_work_fetch[i].busy_time_estimator.reset();
     }
 }