NetbiosAddress mockHost = mock(NetbiosAddress.class);
        SecureRandom mockRandom = mock(SecureRandom.class);

        // Create a machine ID (32 bytes)
        byte[] machineId = new byte[32];
        mockRandom.nextBytes(machineId);

        lenient().when(mockConfig.getDefaultDomain()).thenReturn("TESTDOMAIN");
        lenient().when(mockConfig.isUseUnicode()).thenReturn(true);

        // Use reflection to set private field
        java.lang.reflect.Field machineIdField = BaseConfiguration.class.getDeclaredField("machineId");
        machineIdField.setAccessible(true);
        machineIdField.set(testConfig, customMachineId);

        testConfig.initDefaults();

        assertArrayEquals(customMachineId, testConfig.getMachineId());
    }

    @Test

        this.localTimeZone = TimeZone.getDefault();
        this.random = new SecureRandom();

        if (this.machineId == null) {
            final byte[] mid = new byte[32];
            this.random.nextBytes(mid);
            this.machineId = mid;
        }

        if (this.nativeOs == null) {
            this.nativeOs = System.getProperty("os.name");
        }

Les conteneurs Linux s'exécutent en utilisant le même noyau Linux que l'hôte (machine, machine virtuelle, serveur cloud, etc.). Cela signifie simplement qu'ils sont très légers (comparés à des machines virtuelles complètes émulant un système d'exploitation entier).

Ainsi, les conteneurs consomment **peu de ressources**, une quantité comparable à l'exécution directe des processus (alors qu'une machine virtuelle consommerait beaucoup plus).

Linux containers run using the same Linux kernel of the host (machine, virtual machine, cloud server, etc). This just means that they are very lightweight (compared to full virtual machines emulating an entire operating system).

This way, containers consume **little resources**, an amount comparable to running the processes directly (a virtual machine would consume much more).

    /**
     * A Hybrid node tries to resolve a name using the nameserver first. If
     * that fails use the broadcast address. This is the default if a nameserver
     * is provided. This is the behavior of Microsoft Windows machines.
     */

    public static final int H_NODE = 3;

    /**
     * Unknown MAC Address
     */

### Server Memory { #server-memory }

For example, if your code loads a Machine Learning model with **1 GB in size**, when you run one process with your API, it will consume at least 1 GB of RAM. And if you start **4 processes** (4 workers), each will consume 1 GB of RAM. So in total, your API will consume **4 GB of RAM**.

And if your remote server or virtual machine only has 3 GB of RAM, trying to load more than 4 GB of RAM will cause problems. 🚨

////

## HTML "dfn" elements { #html-dfn-elements }

* <dfn title="A group of machines that are configured to be connected and work together in some way.">cluster</dfn>
* <dfn title="A method of machine learning that uses artificial neural networks with numerous hidden layers between input and output layers, thereby developing a comprehensive internal structure">Deep Learning</dfn>

    /**
     * A Hybrid node tries to resolve a name using the nameserver first. If
     * that fails use the broadcast address. This is the default if a nameserver
     * is provided. This is the behavior of Microsoft Windows machines.
     */

    public static final int H_NODE = 3;

    static final InetAddress[] NBNS = Config.getInetAddressArray("jcifs.smb1.netbios.wins", ",", new InetAddress[0]);

Voir la section `### HTML abbr elements` dans l’invite générale dans `scripts/translate.py`.

////

## Éléments HTML « dfn » { #html-dfn-elements }

* <dfn title="Un groupe de machines configurées pour être connectées et travailler ensemble d’une certaine manière.">grappe</dfn>