Lioran S3 describes multipart uploads as persisted sessions whose parts stream to staging files under a global concurrency limit. A semaphore bounds active part transfers; a mutex coordinates changes to shared session metadata. Uploaded parts remain staged—not yet a visible object—until completion commits the assembled object.
These details come from project-authored technical articles by Swaraj Puppalwar, identified by the project as Founder & CTO at Lioran Group and Lioran Developer Solutions. Lioran S3 is labeled V1 Pre-Alpha, so the implementation details and figures below are the project’s reported design, not independently verified production guarantees.
As an Amazon Associate I earn from qualifying purchases.
How parallel part uploads are bounded
Each active part upload acquires a permit from a global Tokio semaphore. The multipart article reports a global part-concurrency setting of 64. That is a server-side cap on active part work across sessions; it is distinct from the number of parts a client is advised to upload in parallel.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A client can therefore send several parts concurrently, but the server still limits how many part streams are active globally. When permits are occupied, additional work must wait for capacity. The project’s concurrency companion describes this as backpressure: constrain active work rather than allowing incoming transfers to create unlimited simultaneous load. Puppalwar summarizes the design principle: “Concurrency belongs on the data path.” Lioran S3 concurrency architecture
#1 Best Overall
- MADE FOR THE MAKERS: Create; Explore; Store; The T7 Portable SSD delivers fast speeds and durable features to back up any endeavor; Build your video editing empire, file your photographs or back up your blogs all in an instant
- SHARE IDEAS IN A FLASH: Don’t waste a second waiting and spend more time doing; The T7 is embedded with PCIe NVMe technology that brings fast read and write speeds up to 1,050/1,000 MB/s¹, making it almost twice as fast as the T5
- ALWAYS MAKE THE SAVE: Compact design with massive capacity; With capacities up to 4TB, save exactly what you need to your drive – from large working files to game data and everything in between
- ADAPTS TO EVERY NEED: Whether using a PC or mobile phone, count on the T7 for extensive compatibility²; It’s a true team player when it comes to heavy-duty application usage or file-saving
- HI RESOLUTION VIDEO RECORDING: Record Ultra High Resolution (4K 60fs) videos directly onto the T7 Portable SSD with your favorite camera or mobile devices; Supports iPhone 15 Pro Res 4K at 60fps video and more³
This limit does not establish a speed advantage or guarantee a particular throughput. The article gives a configuration value and recommendation, not a benchmark under stated hardware or workload conditions.
Why a mutex does not serialize the file transfers
Several part streams may run at once, while each stream contributes updates to shared session fields such as bytes_received, parts, updated_at, and state. The session-update mutex protects those related changes so concurrent requests do not leave the persisted record inconsistent.
The mutex is a convergence point for shared metadata, not a lock intended to hold the entire part body in a serialized transfer. In Puppalwar’s words, “Serialization belongs around shared mutable state that actually requires it.” This separates parallel data movement from coordinated session bookkeeping. Concurrency architecture details
Rank #2
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
How parts stream into staging files
The described session directory is staging/uploads/<upload-id>/. While a part is arriving, it is written to an .uploading path; after a successful stream, it transitions to a .tmp path. For example, part_00001.uploading becomes part_00001.tmp. The distinction lets the system tell an incomplete transfer from a part that finished streaming.
The article reports a 128 KiB internal copy buffer and incremental SHA-256 calculation while writing. That means the described path need not assemble a complete part in one heap buffer. It does not, by itself, establish a process-wide memory ceiling: total memory use depends on all active work and other implementation details. Lioran S3 bounded-memory streaming
Filesystem names are not simply made from object keys. The storage-layout article says keys remain logical identifiers rather than being used directly as filesystem paths, separating user-facing names from the staging layout. Lioran S3 storage layout
Rank #3
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
What makes an upload resumable
Resumption depends on server-side state, not merely on a client retrying a request. At initialization, Lioran S3 assigns an upload ID and video ID, records expiration information, creates a session directory, and persists a session record through MetadataStore. Later requests can refer to that session and its staged parts rather than treating every retry as a wholly new upload.
In practical terms, a retry is useful only when the server can still identify the session and determine which parts have arrived. The article reports accepted part numbers from 1 through 10,000. A retrying client must work within the session and part numbering rules exposed by the implementation; this description does not establish a universal multipart protocol or AWS SDK compatibility.
Which limits and recommendations does the article report?
The following figures are reported by Swaraj Puppalwar in the Lioran multipart internals article dated October 1, 2026. They are project defaults, bounds, or recommendations—not standards, measured results, or tuning advice proven optimal for every workload.
Rank #4
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| Setting or guidance | Reported value | How to interpret it |
|---|---|---|
| Minimum part size | 5 MiB | Reported lower bound. |
| Maximum part size | 512 MiB | Reported upper bound. |
| Recommended part size | 32 MiB | General recommendation in the article, subject to configured bounds. |
| Adaptive part-size guidance | 16 MiB for payloads up to 1 GiB; 32 MiB above 1 GiB; 64 MiB above 10 GiB | Recommendations subject to configured part-size bounds. |
| Recommended client parallelism | 8 | Client-facing guidance; separate from the server-wide cap. |
| Global active part concurrency | 64 | Reported server-side semaphore setting across sessions. |
| Stream copy buffer | 128 KiB | Reported internal buffer for a part stream. |
| Session time to live | 24 hours | Reported default session TTL. |
| Accepted part numbers | 1–10,000 | Reported range for part numbering. |
The adaptive size guidance has overlapping boundaries as written: “up to 1 GiB,” “above 1 GiB,” and “above 10 GiB.” It does not specify a separate recommendation for exactly 10 GiB, so do not infer a more precise threshold policy than the article states. Puppalwar’s multipart internals article
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How quota checks account for unfinished transfers
Initialization is described as validating the object key and bucket, checking host free space and bucket quota, enforcing an active-session limit, and considering expected payload size. When a part arrives, the quota projection includes committed bucket usage, subtracts an existing object if it is being replaced, then adds bytes already received by the session and the incoming part length.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchCounting bytes already received matters because those bytes are physically staged even though the final object is not committed. A quota check that counted only committed objects would understate space already claimed by uploads in progress. The durability companion discusses disk guardrails and crash-safety considerations; these are project-described safeguards, not an independent verification of their behavior under failure. Lioran S3 durability and disk guardrails
Best Value
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
When the uploaded data becomes an object
Successfully streamed parts remain in staging; they do not yet expose a final assembled object. Completion is the transition into committed-object state, according to the project’s durability article. In other words, the presence of one or more completed part files is not the same as a committed object being visible to readers. Lioran S3 durability and crash-safety notes
What happens to abandoned sessions?
The reported default session TTL is 24 hours. Expiration is important because staged parts occupy real disk space even if the client never finishes. An expired session therefore needs cleanup of its metadata and files to reclaim storage; the articles identify expiry and abandoned data as concerns but do not establish a universal cleanup schedule or a production service-level guarantee.
Scope and compatibility
The project overview describes Lioran S3 as self-hosted, currently single-node object storage with a native REST API and resumable multipart uploads. It explicitly says, “It does not currently expose a drop-in AWS S3 API compatibility layer.” That matters when evaluating whether an AWS-oriented client or workflow can be used unchanged: compatibility should not be assumed from the phrase “S3” alone. Lioran S3 V1 Pre-Alpha project overview
Recommended Free Tools
The overview labels the release V1 Pre-Alpha and warns that APIs, storage formats, protocol details, SDK behavior, and operational assumptions can change. The multipart and companion articles are project-authored descriptions; they do not amount to an independent code audit, crash test, or comparative benchmark.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
