- Sort Score
- Result 10 results
- Languages All
Results 341 - 350 of 412 for 50 (0.02 sec)
-
guava/src/com/google/common/util/concurrent/AbstractFutureState.java
try { helper = new AtomicReferenceFieldUpdaterAtomicHelper(); } catch (Exception // sneaky checked exception | Error atomicReferenceFieldUpdaterFailure) { // Some Android 5.0.x Samsung devices have bugs in JDK reflection APIs that cause // getDeclaredField to throw a NoSuchFieldException when the field is definitely there.
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 34.8K bytes - Viewed (0) -
guava-tests/test/com/google/common/hash/HashTestUtils.java
+ " trials"); } } } } } /** * Test for avalanche with 2-bit deltas. Most probabilities of output bit(j) differing are well * within 50%. */ static void check2BitAvalanche(HashFunction function, int trials, double epsilon) { Random rand = new Random(0); int keyBits = 32; int hashBits = function.bits();
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Mon Aug 11 19:31:30 UTC 2025 - 25.6K bytes - Viewed (0) -
android/guava/src/com/google/common/net/InetAddresses.java
* <li><a target="_parent" href="http://www.space.net/~gert/RIPE/ipv6-filters.html">http://www. * space.net/~gert/RIPE/ipv6-filters.html</a> * </ul> * * @author Erik Kline * @since 5.0 */ @J2ktIncompatible @GwtIncompatible public final class InetAddresses { private static final int IPV4_PART_COUNT = 4; private static final int IPV6_PART_COUNT = 8;
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Feb 19 21:24:11 UTC 2025 - 47.4K bytes - Viewed (0) -
docs/de/docs/deployment/concepts.md
Sie können eine **beliebige Zahl** festlegen, um beispielsweise eine Ressourcenauslastung zwischen **50 % und 90 %** anzustreben. Der Punkt ist, dass dies wahrscheinlich die wichtigen Dinge sind, die Sie messen und verwenden sollten, um Ihre Deployments zu optimieren.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 20.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.23.md
- github.com/golang/mock: [v1.4.4 → v1.5.0](https://github.com/golang/mock/compare/v1.4.4...v1.5.0) - github.com/google/pprof: [1ebb73c → cbba55b](https://github.com/google/pprof/compare/1ebb73c...cbba55b) - github.com/hashicorp/golang-lru: [v0.5.1 → v0.5.0](https://github.com/hashicorp/golang-lru/compare/v0.5.1...v0.5.0)
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Tue Feb 28 21:06:52 UTC 2023 - 424.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.33.md
- github.com/go-logfmt/logfmt: [v0.5.1 → v0.4.0](https://github.com/go-logfmt/logfmt/compare/v0.5.1...v0.4.0) - github.com/golang-jwt/jwt/v4: [v4.5.0 → v4.5.2](https://github.com/golang-jwt/jwt/compare/v4.5.0...v4.5.2) - github.com/golang/glog: [v1.2.1 → v1.2.2](https://github.com/golang/glog/compare/v1.2.1...v1.2.2)
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Aug 13 19:46:23 UTC 2025 - 294.3K bytes - Viewed (0) -
src/test/java/jcifs/internal/smb1/net/NetServerEnum2ResponseTest.java
byte[] dst = new byte[100]; int result = response.writeSetupWireFormat(dst, 0); assertEquals(0, result); // Test with different offset result = response.writeSetupWireFormat(dst, 50); assertEquals(0, result); } @Test @DisplayName("Test writeParametersWireFormat returns 0") void testWriteParametersWireFormat() { byte[] dst = new byte[100];
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 25.4K bytes - Viewed (0) -
docs/pt/docs/advanced/settings.md
/// Assim, o atributo `admin_email` seria definido como `"******@****.***"`. `app_name` seria `"ChimichangApp"`. E `items_per_user` manteria o valor padrão de `50`. ## Configurações em um módulo separado
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Wed Jan 15 20:17:23 UTC 2025 - 15.8K bytes - Viewed (0) -
docs/es/docs/deployment/concepts.md
Podrías establecer un **número arbitrario** para alcanzar, por ejemplo, algo **entre 50% a 90%** de utilización de recursos. El punto es que esas son probablemente las principales cosas que querrás medir y usar para ajustar tus implementaciones.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun May 11 13:37:26 UTC 2025 - 19.3K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
You could put an **arbitrary number** to target, for example, something **between 50% to 90%** of resource utilization. The point is that those are probably the main things you will want to measure and use to tweak your deployments.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 18.6K bytes - Viewed (0)