what is the use-case behind this change can you explain a bit?

what is the use-case behind this change can you explain a bit?

We can use tier 2 disks with big files in multipart, much less IO for hard disks and much less stress for disks.

what is the use-case behind this change can you explain a bit?
Thank you for reviewing the pull request. The primary use cases motivating this change are as follows:

1. Small-File Intensive Scenarios (e.g., IoT/edge devices):
   The default minimum part size of 5 MiB forces small files (e.g., 1–2 MiB sensor logs) into single-part uploads, thereby negating the performance benefits associated with multipart parallelism.
   By configuring a smaller value (e.g., 1 MiB), multipart uploads can be utilized even for very small objects, thereby improving throughput through concurrent transfers.

2. Operational Flexibility:
   Avoiding Recompilation – Currently, adjusting the minPartSize requires custom recompilation. Enabling dynamic configuration via the MINIO_PART_SIZE_MIN environment variable simplifies deployment and enhances configurability without the need for rebuilding the application.