Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 1 - 10 of 426 for cores (0.03 seconds)

  1. build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/info/GlobalBuildInfoPlugin.java

                                if (name.equals("physical id")) {
                                    currentID = value;
                                }
                                // Number of cores not including hyper-threading
                                if (name.equals("cpu cores")) {
                                    assert currentID.isEmpty() == false;
                                    socketToCore.put("currentID", Integer.valueOf(value));
    Created: Wed Apr 08 16:19:15 GMT 2026
    - Last Modified: Tue Aug 17 10:02:58 GMT 2021
    - 18.1K bytes
    - Click Count (0)
  2. benchmarks/src/main/java/org/elasticsearch/benchmark/search/aggregations/AggConstructionContentionBenchmark.java

    import java.util.function.Function;
    
    /**
     * Benchmarks the overhead of constructing {@link Aggregator}s in many
     * parallel threads. Machines with different numbers of cores will see
     * wildly different results running this from running this with more
     * cores seeing more benefits from preallocation.
     */
    @Fork(2)
    @Warmup(iterations = 10)
    @Measurement(iterations = 5)
    @BenchmarkMode(Mode.AverageTime)
    Created: Wed Apr 08 16:19:15 GMT 2026
    - Last Modified: Wed Jun 16 08:22:22 GMT 2021
    - 12.3K bytes
    - Click Count (0)
  3. build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/precommit/ThirdPartyAuditTask.java

                .getResolvedConfiguration()
                .getFiles(reallyThirdParty);
            // don't scan provided dependencies that we already scanned, e.x. don't scan cores dependencies for every plugin
            if (compileOnlyConfiguration != null) {
                jars.removeAll(compileOnlyConfiguration);
            }
            return jars;
        }
    
        @TaskAction
    Created: Wed Apr 08 16:19:15 GMT 2026
    - Last Modified: Thu Jun 17 08:59:22 GMT 2021
    - 16.2K bytes
    - Click Count (0)
  4. docs/config/README.md

    `max_sleep` to a *lower* value and setting `max_io` to a *higher* value would make heal go faster.
    
    Each node is responsible of healing its local drives; Each drive will have multiple heal workers which is the quarter of the number of CPU cores of the node or the quarter of the configured nr_requests of the drive (https://www.kernel.org/doc/Documentation/block/queue-sysfs.txt). It is also possible to provide a custom number of workers by using this command: `mc admin config set alias/ heal...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 18.1K bytes
    - Click Count (1)
  5. docs/bigdata/README.md

    ![hdfs-configs](https://github.com/minio/minio/blob/master/docs/bigdata/images/image2.png?raw=true "hdfs advanced configs")
    
    Navigate to **Custom core-site** to configure MinIO parameters for `_s3a_` connector
    
    ![s3a-config](https://github.com/minio/minio/blob/master/docs/bigdata/images/image5.png?raw=true "custom core-site")
    
    ```
    sudo pip install yq
    alias kv-pairify='yq ".configuration[]" | jq ".[]" | jq -r ".name + \"=\" + .value"'
    ```
    
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 14.7K bytes
    - Click Count (0)
  6. docs/en/docs/deployment/concepts.md

    ### Multiple Processes - Workers { #multiple-processes-workers }
    
    If you have more clients than what a single process can handle (for example if the virtual machine is not too big) and you have **multiple cores** in the server's CPU, then you could have **multiple processes** running with the same application at the same time, and distribute all the requests among them.
    
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 05 18:13:19 GMT 2026
    - 18.5K bytes
    - Click Count (1)
  7. MIGRATION.md

    #### Configuration Migration
    
    Map Solr configuration to Fess:
    
    | Solr Feature | Fess Equivalent |
    |--------------|----------------|
    | Solr Core | Fess doesn't use cores; all documents in one index |
    | Schema Fields | Define in crawl configuration or use default fields |
    | RequestHandlers | Use Fess JSON API with parameters |
    | Facet Fields | Configure in Fess search settings |
    Created: Tue Mar 31 13:07:34 GMT 2026
    - Last Modified: Thu Nov 06 12:40:11 GMT 2025
    - 23.2K bytes
    - Click Count (0)
  8. api/maven-api-core/src/main/java/org/apache/maven/api/Constants.java

        /**
         * ProjectBuilder parallelism.
         *
         * @since 4.0.0
         */
        @Config(type = "java.lang.Integer", defaultValue = "cores/2 + 1")
        public static final String MAVEN_MODEL_BUILDER_PARALLELISM = "maven.modelBuilder.parallelism";
    
        /**
         * User property for enabling/disabling the consumer POM feature.
         *
         * @since 4.0.0
    Created: Sun Apr 05 03:35:12 GMT 2026
    - Last Modified: Tue Dec 16 13:41:14 GMT 2025
    - 28.7K bytes
    - Click Count (0)
  9. TESTING.asciidoc

    ------------------------------------------------------------------
    
    === Load balancing and caches.
    
    By default the tests run on multiple processes using all the available cores on all
    available CPUs. Not including hyper-threading.
    If you want to explicitly specify the number of JVMs you can do so on the command
    line:
    
    ----------------------------
    ./gradlew test -Dtests.jvms=8
    Created: Wed Apr 08 16:19:15 GMT 2026
    - Last Modified: Mon Jun 07 13:55:20 GMT 2021
    - 32.5K bytes
    - Click Count (0)
  10. docs/en/docs/deployment/docker.md

    process** (e.g. a Uvicorn process running your FastAPI application). They would all be **identical containers**, running the same thing, but each with its own process, memory, etc. That way you would take advantage of **parallelization** in **different cores** of the CPU, or even in **different machines**.
    
    And the distributed container system with the **load balancer** would **distribute the requests** to each one of the containers with your app **in turns**. So, each request could be handled...
    Created: Sun Apr 05 07:19:11 GMT 2026
    - Last Modified: Thu Mar 05 18:13:19 GMT 2026
    - 28.3K bytes
    - Click Count (1)
Back to Top