And then, right after the `yield`, we unload the model. This code will be executed **after** the application **finishes handling requests**, right before the *shutdown*. This could, for example, release resources like memory or a GPU.

/// tip

The `shutdown` would happen when you are **stopping** the application.

Maybe you need to start a new version, or you just got tired of running it. 🤷

///

All Go pointers passed to C must point to pinned Go memory. Go pointers
passed as function arguments to C functions have the memory they point to
implicitly pinned for the duration of the call. Go memory reachable from
these function arguments must be pinned as long as the C code has access
to it. Whether Go memory is pinned is a dynamic property of that memory
region; it has nothing to do with the type of the pointer.

        public long used;
        /** Committed non-heap memory in bytes */
        public long committed;
        /** Maximum non-heap memory in bytes */
        public long max;
        /** The percentage of non-heap memory usage. */
        public short percent;
    }

    /**
     * Data transfer object representing JVM buffer pool statistics.
     */

 */
package jcifs.internal.smb2.rdma;

/**
 * RDMA memory access permissions for registered memory regions.
 * These flags control what operations can be performed on a memory region.
 */
public enum RdmaAccess {
    /**
     * Local read access to the memory region
     */
    LOCAL_READ,

    /**
     * Local write access to the memory region
     */
    LOCAL_WRITE,

    /**

      MockResponse
        .Builder()
        .onRequestBody(CloseSocket())
        .build(),
    )
    // Limit the size of the request body that the server holds in memory to an arbitrary
    // 3.5 MBytes so this test can pass on devices with little memory.
    server.bodyLimit = 7 * 512 * 1024
    val connection = server.url("/").toUrl().openConnection() as HttpURLConnection
    connection.requestMethod = "POST"

* Restarts
* Replication (the number of processes running)
* Memory
* Previous steps before starting

## Memory { #memory }

If you run **a single process per container** you will have a more or less well-defined, stable, and limited amount of memory consumed by each of those containers (more than one if they are replicated).

					success = false
				} else {
					stopFn(oi, nil)
				}
				ri.trackCurrentBucketObject(r.Target.Bucket, oi, success, attempts)
				globalBatchJobsMetrics.save(job.ID, ri)
				// persist in-memory state to disk after every 10secs.
				batchLogIf(ctx, ri.updateAfter(ctx, api, 10*time.Second, job))

				if wait := globalBatchConfig.ReplicationWait(); wait > 0 {
					time.Sleep(wait)
				}
			}()
		}
		wk.Wait()

import jcifs.internal.smb2.rdma.RdmaMemoryRegion;

/**
 * DiSNI memory region implementation.
 *
 * This class would integrate with DiSNI to provide registered
 * memory regions for high-performance RDMA operations.
 *
 * Note: This is a skeleton implementation. A real implementation would
 * require proper DiSNI integration with actual memory registration.
 */
public class DisniMemoryRegion extends RdmaMemoryRegion {

 * <p>This class should not be assumed to be universally superior to {@code java.util.HashMap}.
 * Generally speaking, this class reduces object allocation and memory consumption at the price of
 * moderately increased constant factors of CPU. Only use this class when there is a specific reason
 * to prioritize memory over CPU.
 *
 * @author Louis Wasserman
 * @author Jon Noack
 */
@GwtIncompatible // not worth using in GWT for now

 * it requires that the complete universe of rows and columns be specified at construction time.
 * Second, it is always backed by an array large enough to hold a value for every possible
 * combination of row and column keys. (This is rarely optimal unless the table is extremely dense.)
 * Finally, every possible combination of row and column keys is always considered to have a value