iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Lioran S3’s described multipart-upload path streams parts concurrently while bounding active server work with a semaphore, persisting session state for retries, and staging incoming files separately from the final object. An upload does not become a committed object just because its parts have arrived: completion is the visibility transition. These details come from project-authored technical articles, not an independent code audit or performance test.
How multipart uploads are coordinated
“Large uploads are not just normal PUTs with bigger numbers,” writes Swaraj Puppalwar, Founder & CTO at Lioran Group and Lioran Developer Solutions, in the project’s multipart internals article. The described design separates streaming data work from updates to shared session metadata.
A semaphore bounds active part streams
Each active part upload acquires a permit from a global Tokio semaphore. Puppalwar reports a global part-concurrency setting of 64. This is a server-side cap across upload sessions; it is distinct from how many parts an individual client is advised to send in parallel. The concurrency architecture article describes the semaphore as backpressure: when permits are occupied, additional work must wait rather than starting unlimited part streams.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A mutex protects the session update path
Concurrent parts affect shared fields such as bytes_received, parts, updated_at, and state. The manager uses a session-update mutex to keep those changes coherent. The lock is for shared mutable state, not for serializing every byte in every transfer. As Puppalwar puts it, “Concurrency belongs on the data path.” and “Serialization belongs around shared mutable state that actually requires it.”
#1 Best Overall
- 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
What happens to part data on disk
The project describes a staging directory at staging/uploads/<upload-id>/. While an incoming part is being written, it uses an .uploading filename; after a successful stream, it transitions to a .tmp file. For example, part_00001.uploading becomes part_00001.tmp. This distinction lets the system distinguish an unfinished transfer from a part whose stream completed.
Object keys remain logical identifiers rather than becoming filesystem paths, according to the project’s storage-layout article. The staged parts and upload-session record are separate from the final committed object.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
How resuming an interrupted upload works
Retrying a part request alone is not enough to make an upload resumable. The server needs state that connects later requests to the same upload. Lioran’s described initialization assigns an upload ID and video ID, records expiration information and the upload directory, and persists a session record through MetadataStore.
Free tools Windows power users keep installed
One-click scans. No signup required.
That persisted record gives subsequent requests a session to resume and update. The article reports an accepted part-number range of 1 through 10,000. It does not establish client-specific retry behavior, nor does the project material cited here describe a universal recovery guarantee after every possible failure.
Rank #3
- Capacity Display Variance: 500GB external ssd often appears as around 465GB on Windows. MacOS can show full 500 GB capacity. This is binary calculation difference and doesn’t affect SSD hard drive actual physical storage
- 1050 MB/s Speed: Instantly access to your files with blazing-fast 10Gbps external SSD read up to 1050MB/s and write up to 1000MB/s. LED Light indicates USB SSD instant activity
- Data Security: Solid state drives S.M.A.R.T. health diagnostics and adaptive TRIM optimizing data block management ensures consistent write speeds and extends the longevity of the portable SSD
- USB-C & USB-A Cable: Both cables featuring rapid USB 3.2 Gen2, this USB SSD effortlessly bridges devices, enabling seamless cross-platform file transfers and backup between computers, smartphones, tablets and iPhone
- Always Fast: No slowdowns for large file transfers. With SLC caching (25% of current available capacity allocated as high-speed cache), this external SSD delivers steady 10Gbps for transfers within the cache capacity
When parts become a visible object
Uploaded parts are staged data, not a final object that clients can already read as committed. The project’s durability and crash-safety article describes completion as the transition into committed-object state. In other words, receipt of individual parts and publication of the assembled object are separate stages.
How memory use and integrity are handled
The multipart article reports a 128 KiB internal copy buffer and incremental SHA-256 calculation while writing. The accompanying bounded-memory streaming article describes the same streaming approach: the implementation need not hold an entire part in one heap buffer to process it. The reported buffer is an implementation detail, not a guarantee about total process memory; concurrent requests and other work also consume resources.
Rank #4
- 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³
Quota checks, expiry, and abandoned uploads
In-progress bytes count toward quota
At initialization, the described path validates the object key and bucket, checks host free space and bucket quota, considers active-session count, and validates expected payload size. For an arriving part, its quota projection includes committed bucket usage, subtracts an existing object being replaced, adds bytes already received by this session, and adds the incoming part length. Counting the session’s received bytes matters because those bytes already occupy storage; ignoring them would understate projected usage.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Expired sessions need cleanup
Puppalwar reports a default session TTL of 24 hours. An abandoned upload can leave staged files consuming physical disk space until the expired session and its files are cleaned up. Expiration is therefore a storage guardrail as well as a limit on how long a session remains resumable. The cited material states the TTL but does not establish a cleanup schedule or a guarantee that cleanup happens immediately at the expiration instant.
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.
Reported limits and recommendations
The following are values and recommendations reported by Puppalwar in the Lioran multipart internals article dated October 1, 2026. They are not standards, measured performance results, or universal tuning advice; some are configurable guardrails.
| Setting or guidance | Reported value | How to interpret it |
|---|---|---|
| Minimum part size | 5 MiB | Reported lower bound |
| Recommended part size | 32 MiB | Project recommendation, not a workload-specific optimum |
| Maximum part size | 512 MiB | Reported upper bound |
| Recommended client parallelism | 8 | Recommendation for parallel parts, separate from the global server cap |
| Global part concurrency | 64 | Reported server-side semaphore setting across sessions |
| Internal stream copy buffer | 128 KiB | Reported per-copy buffer, not total memory usage |
| Accepted part numbers | 1 through 10,000 | Reported range |
| Default session TTL | 24 hours | Reported session lifetime before expiry |
The same article gives this adaptive part-size recommendation, subject to configured bounds:
- 16 MiB for payloads up to 1 GiB.
- 32 MiB for payloads above 1 GiB.
- 64 MiB for payloads above 10 GiB.
These recommendations do not establish that one part size or parallelism level will be fastest for a particular network, client, disk, or workload.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsScope and release caveats
The project overview, posted October 1, 2026, labels Lioran S3 V1 Pre-Alpha and warns that APIs, storage formats, protocol details, SDK behavior, and operational assumptions may change. It describes the system as self-hosted and currently single-node. Puppalwar writes of the current release: “It does not currently expose a drop-in AWS S3 API compatibility layer.” These qualifications matter: the multipart behavior here is what the project describes for this pre-alpha, not a guarantee about all S3-compatible storage or a verified production contract.
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.
