Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

Object tiering is the moving of the data of an object from one set of hardware to another set of hardware. This is often done as a cost-saving measure, keeping more expensive and performant hardware for the newest or most accessed objects while placing other objects to less expensive and less performant storage solutions. Retrieve a tiered object When MinIO AIStor moves an object to another tier, the object’s metadata remains on the primary tier while the object’s data moves to the secondary tier. When MinIO AIStor needs to serve a tiered object, it transparently retrieves the object from the secondary tier.

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

MinIO AIStor supports deploying resources onto Windows hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of Windows. For testing or local development using a virtualized environment, including Windows Subsystem for Linux (WSL), use a machine with a higher number of cores and 16 or 32GB of RAM.

MinIO AIStor is licensed under the MinIO Software License. An active license is required for production deployments. This procedure downloads and installs the AIStor Server onto a host running Microsoft Windows Server or Windows 11 Professional Edition. Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. Procedure Download the AIStor Server binary Invoke-WebRequest https://dl.min.io/aistor/minio/release/windows-amd64/minio -OutFile C:\minio.exe Create a data directory for use with the server The following example uses the path $HOME/minio/data. Changes this path to reflect the folder, storage volume, or drive intended for use with the server.

MinIO AIStor supports deploying resources as a container for local development and evaluation. Setting up MinIO AIStor as a container involves these steps: Deploy MinIO AIStor as a container Set up network encryption (optional) Performance The following table shows areas that have the greatest impact on MinIO AIStor performance, listed in order of importance.

Skip to Main Content Documentation Home MySQL 8.0 Reference Manual Related Documentation MySQL 8.0 Release Notes MySQ...

MinIO AIStor supports compressing objects to reduce disk usage. Objects are compressed on PUT before writing to disk, and uncompressed on GET before they are sent to the client. This makes the compression process transparent to client applications and services. Depending on the type of data, compression may also increase overall throughput. Write throughput for a production deployment is generally 500MB per second or greater per available CPU core in the system. Decompression is approximately 1 GB per second or greater for each CPU core.

The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary MinIO AIStor deployment to a bucket on a remote MinIO AIStor deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” MinIO AIStor deployment using NVMe storage to a “warm” MinIO AIStor deployment using SSD. Requirements Install and configure mc This procedure uses mc for performing operations on the MinIO AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.