Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 31 - 37 of 37 for warmups (0.06 seconds)

  1. .teamcity/src/main/kotlin/configurations/CompileAll.kt

        stage: Stage,
    ) : OsAwareBaseGradleBuildType(os = Os.LINUX, stage = stage, init = {
            id(buildTypeId(model))
            name = "Compile All"
            description = "Compiles all production/test source code and warms up the build cache"
    
            features {
                publishBuildStatusToGithub(model)
            }
    
            applyDefaults(
                model,
                this,
    Created: Wed Apr 01 11:36:16 GMT 2026
    - Last Modified: Mon Dec 22 07:15:16 GMT 2025
    - 1.4K bytes
    - Click Count (0)
  2. internal/bpool/bpool.go

    		panic("minimum buffer length cannot be > capacity of the buffer")
    	}
    	return &BytePoolCap{
    		c:    make(chan []byte, maxSize),
    		w:    width,
    		wcap: capwidth,
    	}
    }
    
    // Populate - populates and pre-warms the byte pool, this function is non-blocking.
    func (bp *BytePoolCap) Populate() {
    	for _, buf := range reedsolomon.AllocAligned(cap(bp.c), bp.wcap) {
    		bp.Put(buf[:bp.w])
    	}
    }
    
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Sep 28 20:59:21 GMT 2025
    - 3K bytes
    - Click Count (0)
  3. android/guava-tests/test/com/google/common/util/concurrent/UninterruptiblesTest.java

      /*
       * RE: the WaitNotInLoop warnings:
       *
       * Our tests for awaitUninterruptibly are written under the assumption that no spurious wakeups
       * occur except for those produced by awaitUninterruptibly itself in response to interrupts.
       *
       * This isn't guaranteed to work, so any further spurious wakeups would probably cause failures in
       * tests that assert that a certain amount of time has passed, that the method returned `false`,
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Mon Mar 16 22:45:21 GMT 2026
    - 38.1K bytes
    - Click Count (0)
  4. guava-tests/test/com/google/common/util/concurrent/UninterruptiblesTest.java

      /*
       * RE: the WaitNotInLoop warnings:
       *
       * Our tests for awaitUninterruptibly are written under the assumption that no spurious wakeups
       * occur except for those produced by awaitUninterruptibly itself in response to interrupts.
       *
       * This isn't guaranteed to work, so any further spurious wakeups would probably cause failures in
       * tests that assert that a certain amount of time has passed, that the method returned `false`,
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Mon Mar 16 22:45:21 GMT 2026
    - 38.1K bytes
    - Click Count (0)
  5. android/guava/src/com/google/common/util/concurrent/SmoothRateLimiter.java

       *
       * <pre>
       *          ^ throttling
       *          |
       *    cold  +                  /
       * interval |                 /.
       *          |                / .
       *          |               /  .   ← "warmup period" is the area of the trapezoid between
       *          |              /   .     thresholdPermits and maxPermits
       *          |             /    .
       *          |            /     .
       *          |           /      .
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Wed May 14 19:40:47 GMT 2025
    - 19.3K bytes
    - Click Count (0)
  6. android/guava/src/com/google/common/util/concurrent/Uninterruptibles.java

         * to return. Fortunately, a wait on a Condition is allowed to return early on account of a
         * "spurious wakeup," so we're allowed to convert interruptions into such wakeups.
         */
    
        /*
         * Since we can't loop inside awaitUninterruptibly(Condition, ...), the user is responsible for
         * calling us again in case of interrupt. Then, if we were to call await(...) immediately, as we
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Thu Jan 29 23:24:32 GMT 2026
    - 22.5K bytes
    - Click Count (0)
  7. RELEASE.md

    *   Added warmup capabilities to `tf.keras.optimizers.schedules.CosineDecay` learning rate scheduler. You can now specify an initial and target learning rate, and our scheduler will perform a linear interpolation between the two after which it will begin a decay phase....
    Created: Tue Apr 07 12:39:13 GMT 2026
    - Last Modified: Mon Mar 30 18:31:38 GMT 2026
    - 746.5K bytes
    - Click Count (3)
Back to Top