@@ -315,11 +315,13 @@
 
   (thread-sleep! (cond ;; BB: check with Matt.  Should this sleep move
 		       ;; to cond clauses below where we determine we
 		       ;; have too many jobs running rather than each
 		       ;; time the and condition above is true (which
-		       ;; seems like always)?
+		  ;; seems like always)?
+		  ((< (- (current-seconds)(runs:dat-beginning-of-time runsdat)) 30) ;; for the first 30 seconds do not throttle in any way
+		   0)
         	  ((> (runs:dat-can-run-more-tests-count runsdat) 20) ;; original intent was - save cycles, wait a long time
 		   (if (runs:lownoise "waiting on tasks" 60)(debug:print-info 2 *default-log-port* "waiting for tasks to complete, sleeping briefly ..."))
 		   10)  ;; obviously haven't had any work to do for a while
 		  (else 0)))
 ;;		   ;; if have a number for inter-test-delay, use it, else don't delay much, maybe even zero?
@@ -1192,11 +1194,11 @@
      ((not have-resources) ;; simply try again after waiting a second
       (if (runs:lownoise "no resources" 60)
 	  (debug:print-info 1 *default-log-port* "no resources to run new tests, waiting ..."))
       ;; Have gone back and forth on this but db starvation is an issue.
       ;; wait one second before looking again to run jobs.
-      (thread-sleep! 1)
+      (thread-sleep! 0.25)
       ;; could have done hed tal here but doing car/cdr of newtal to rotate tests
       (list (car newtal)(cdr newtal) reg reruns))
      
      ;; This is the final stage, everything is in place so launch the test
      ;;