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
Configure the Google Drive remote first, then identify which phase is slow before changing flags. Recursive listing and comparison, API overhead for many small files, and the transfer of large-file payloads have different bottlenecks. --fast-list can reduce listing requests, --drive-chunk-size affects upload buffering, and --transfers/--checkers control parallel work—but none is a universal speed fix.
Understand which part of the job is slow
A command can appear “slow” while spending most of its time doing work other than moving file bytes. Separate the run into these phases:
| Phase | What rclone is doing | Typical constraint | Settings that may matter |
|---|---|---|---|
| Listing and comparison | Walking folders, reading metadata, and deciding what needs to be copied | Directory count, API request count, latency, checker workload, or local metadata processing | --fast-list, cautious --checkers changes |
| Per-file API activity | Opening, creating, checking, and finalizing many individual objects | Drive request limits and per-file overhead | Workload shape and moderate parallelism; no flag removes Drive-side limits |
| Payload transfer | Uploading or downloading file contents | Connection capacity, local disk, file size, and upload chunk buffering | --drive-chunk-size for uploads; --transfers for concurrent files |
Start with a verbose baseline rather than changing several options at once. For a representative directory, note the elapsed time, file count, total bytes, memory use, retries, and whether the delay occurs before the first data transfer or while bytes are moving. Use rclone’s progress and verbose output appropriate to your environment, and preserve the log so a later comparison uses the same evidence. The official Drive backend documentation is the reference for backend behavior: rclone Google Drive backend.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Create and verify the Google Drive remote
Interactive OAuth setup
- Run
rclone config. - Choose the option to create a new remote and give it a clear name, such as
drive-main. - Select Google Drive as the storage type.
- Follow the browser-based OAuth flow and approve only the access needed for the job.
- Return to the terminal and let rclone save the remote configuration.
The Drive backend lists scopes that include full Drive access and read-only access. Choose the least-privileged scope that still supports your task. Do not paste OAuth tokens or credential JSON into public issue reports, shared shell history, or verbose logs.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Use a personal API client when appropriate
The Drive documentation says rclone’s shared client ID is being retired during 2026 and recommends creating a personal Google API client. This notice is time-sensitive: check the current instructions on the Drive backend page while configuring a new machine, because Google and rclone requirements can change.
Unattended machines and service accounts
For automation without a browser, the Drive backend supports service-account credentials. Create or select a service account according to Google’s current procedure, configure its credentials through rclone’s Drive options, and grant that account access to the files or shared folders it must process. A service account does not automatically see a user’s private My Drive files; permissions and shared-drive membership still have to be correct.
Verify the destination before a long run
Use a small, non-critical directory for the first copy. A basic copy has this shape:
rclone copy /local/path drive-main:destination/pathcopy adds or updates destination files without making the destination an exact mirror. Use sync only when mirroring is intentional:
rclone sync /local/path drive-main:destination/pathSync can delete destination files that are absent from the source. Confirm the source, remote name, and destination path before using it on valuable data, and begin with a limited test set.
Use --fast-list for listing-heavy jobs
--fast-list changes how rclone builds recursive listings. The Drive backend combines multiple parent-folder listing filters into fewer requests—up to 50 parent filters in one request according to its documentation. This can help when a tree contains many directories and the delay is metadata traversal or comparison rather than file content.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
The trade-off is memory: rclone retains more listing information locally. It does not make an individual upload or download send bytes faster. Test it on a representative tree and compare both runtime and peak memory:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
rclone copy /local/path drive-main:destination/path --fast-listKeep the option when the listing phase measurably improves without exhausting memory. Omit it when the host is memory-constrained or when the job is dominated by large payload transfers and listing is already brief. Example timings shown in documentation are illustrative tests, not a current promise for your account, network, or directory layout.
Choose an upload chunk size without exhausting memory
--drive-chunk-size applies to Drive uploads. The documented default is 8 MiB, and the value must be a power of two of at least 256 KiB. A larger chunk can improve performance for large uploads, but rclone buffers one chunk in memory for every active transfer. In the project’s wording: “Making this larger will improve performance, but note that each chunk is buffered in memory one per transfer.” See the Drive backend documentation and the command reference.
For example, a 64 MiB chunk with four simultaneous transfers can require roughly 256 MiB just for those upload buffers, before rclone, the operating system, filesystem cache, and other processes are counted. That is an illustrative multiplication, not a complete memory forecast. Increase the value gradually while watching peak memory and error behavior:
rclone copy /local/path drive-main:destination/path --drive-chunk-size 32MUse this setting for large-file upload workloads. It is not a download tuning control. On a small-memory host or a job with many concurrent files, a large chunk can cause swapping or out-of-memory failures and make the transfer slower overall. Lowering the chunk reduces per-transfer memory but can reduce upload performance.
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 errorsAdjust transfers and checkers one variable at a time
General rclone defaults are four simultaneous transfers and eight checkers. Transfers control concurrent file movement; checkers perform parallel comparison work and are used as a broader parallelism control in several parts of rclone. The defaults are a starting point, not a target.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
| Option | Documented default | May help when | Risks of increasing it |
|---|---|---|---|
--transfers |
4 | The connection, disk, and Drive backend can sustain several payloads at once | More memory (including chunk buffers), request pressure, contention, and throttling |
--checkers |
8 | Metadata comparison is the measurable bottleneck and the backend tolerates more parallel checks | More API requests, CPU use, and pressure on a slow or rate-limited backend |
--max-connections |
Not a routine speed setting | An advanced configuration requires explicit connection control | The documentation warns it may not map one-to-one to TCP/HTTP connections and some configurations can deadlock |
Try one controlled change, record elapsed time, memory, errors, and request-related failures, then keep or revert it. If increasing transfers does not raise payload throughput, the limit may be Drive, the local disk, or the network rather than available concurrency. If listing becomes slower or errors increase after raising checkers, return toward the default; the general documentation notes that slow backends may need fewer checkers. The general flag descriptions are in rclone’s documentation.
For a controlled test, keep the remote, source subset, and destination constant. First try the defaults, then test a modest transfer-count change such as four to six while leaving checkers unchanged. On a listing-heavy run, reverse the experiment: leave transfers at the baseline and make a small checker adjustment. This isolates whether payload work or metadata work responds. A setting that helps one phase can make another phase worse, so judge the complete run rather than a short burst of progress output.
Expect a different result from small files
Google Drive’s API work is performed per file. The Drive backend documentation warns that Drive rate limiting can constrain rclone to about two transferred files per second, while an individual large file may transfer much faster. This is a general backend limitation note, not a guaranteed, account-specific quota for every current run.
Consequently, a folder containing tens of thousands of small files can take a long time even when a multi-gigabyte test file reaches high network throughput. More transfers may increase request pressure without overcoming the limit. Diagnose this pattern by comparing file count and size distribution, checking whether the log shows long gaps between file completions, and distinguishing the metadata phase from the payload phase. Do not use a large-file result to promise a small-file result.
Chunk size is especially easy to misapply here. It changes how an upload payload is buffered; it does not remove the API calls needed to create, check, and finalize each object. For a small-file archive, the useful measurement is completed files per unit of time and the number of retries, not only the network meter. If the job is limited by Drive-side request handling, a higher --transfers value can add contention without improving that rate.
A repeatable tuning workflow
- Record the baseline. Use the same source subset and destination path for each trial. Capture file count, total bytes, elapsed time, peak memory, retries, and errors.
- Classify the workload. Mark it as listing-heavy (many folders), small-file-heavy (many individual objects), large-file-heavy, or mixed. The classification determines which setting is worth testing.
- Test listing behavior. If the run spends most of its time discovering and comparing files, run the same representative tree with
--fast-list. Keep the result only if memory remains safe and total time improves. - Test upload buffering. For large uploads, increase
--drive-chunk-sizeone power-of-two step at a time. Monitor memory per concurrent transfer and stop if swapping, allocation failures, or retries appear. - Test parallelism. Change
--transfersor--checkers, not both simultaneously. Compare throughput and API errors with the baseline. - Check the physical path. Verify local disk read speed, destination disk space for temporary buffering, network stability, and CPU or memory pressure before attributing every delay to Drive.
- Keep a practical configuration. Choose the fastest stable result, not the highest numerical setting. A slightly slower run that avoids retries, throttling, or out-of-memory failures is usually the better automation setting.
Run each trial long enough to include the same mix of directories and files. A short sample containing one large file can hide the cost of thousands of small objects. For repeatability, write down the rclone version, operating-system environment, remote type, source size distribution, and flags used. These details explain why two otherwise similar machines can produce different results without implying that one undocumented setting is universally superior.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Match the setting to the symptom
| Observed symptom | First action | What not to assume |
|---|---|---|
| No files move for a long time at the start | Inspect verbose timing and test --fast-list on the same tree |
That the network upload is slow |
| Large files transfer steadily but a directory of tiny files crawls | Measure completed files per unit time and account for Drive’s documented rate-limit behavior | That larger upload chunks will solve per-file API overhead |
| Upload throughput is low and memory is plentiful | Test a modestly larger --drive-chunk-size |
That the flag improves downloads |
| Memory spikes or the host swaps | Reduce chunk size, transfers, or both; retest | That more concurrency is always faster |
| More checkers produce API errors or no speed gain | Return toward the default and test fewer checkers | That checker count bypasses backend limits |
| Runs fail only when using sync | Verify source and destination semantics and inspect deletion-related messages | That sync is equivalent to copy |
Operational and security checks
- Use a dedicated remote name for each account, project, or service account so scripts do not silently target the wrong Drive.
- Grant a service account access to the exact files, folders, or shared drives it must process; credentials alone do not grant visibility.
- Protect the rclone configuration and credential files with the host’s normal file permissions and secret-management controls.
- Redact tokens, client secrets, and credential JSON before sharing logs.
- For destructive mirroring, validate a small directory first and confirm that files absent from the source really should disappear from the destination.
- Recheck the live Drive backend documentation when creating a new client ID, because the shared-client retirement notice applies during 2026 and may be updated.
Keep credentials out of command arguments when your shell records history, and avoid turning on verbose logging in a way that exposes authorization material. When moving a remote between machines, use the documented configuration and secret-management process rather than copying secrets into tickets or chat. A correctly tuned transfer is still a failure if it targets the wrong account or leaks its token.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat a “fast” configuration actually looks like
There is no universally optimal combination of flags. A large-file upload on a memory-rich host may benefit from a larger upload chunk and moderate transfer concurrency. A deeply nested tree may benefit from --fast-list if the host has enough memory. A small-file archive may remain slow because Drive’s per-file request limits dominate, regardless of concurrency. The correct configuration is the one that shortens the measured bottleneck without creating memory pressure, retries, or unsafe synchronization behavior.
Use the official references for option syntax and changing backend behavior: Google Drive backend, general rclone documentation, and command reference.
Frequently Asked Questions
How do I speed up rclone with Google Drive?
Measure whether listing, per-file API work, or payload transfer is slow. Then test --fast-list for listing-heavy trees, a modestly larger --drive-chunk-size for large uploads, or cautious --transfers/--checkers changes. Test one variable at a time; no flag bypasses Drive-side limits.
What is the default Google Drive upload chunk size?
The documented default for --drive-chunk-size is 8 MiB. Values must be powers of two and at least 256 KiB. Larger values may improve uploads but consume that amount of buffer memory per active transfer.
Does --fast-list make uploads faster?
No. It reduces listing transactions and can shorten recursive discovery or comparison. It does not increase the byte rate of an individual upload or download, and it uses more memory.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Why is rclone slow with many small files?
Each object requires Drive API activity. The Google Drive backend documentation notes that rate limiting can constrain rclone to about two transferred files per second, although an individual large file can move much faster. This is a general limitation note, not a guaranteed account-specific quota.
Should I increase --transfers above four?
Four is the documented general default. Increase it only if a representative test shows that your connection, disk, memory, and Drive workload benefit. More concurrent transfers can increase memory use, request pressure, throttling, and errors.
Should I increase --checkers above eight?
Eight is the documented general default. More checkers may help when metadata comparison is the measured bottleneck, but slow backends may need fewer. Test separately from transfer-count changes and watch API errors.
Recommended Free Tools
Can I use --drive-chunk-size to speed downloads?
No. The option controls Drive upload chunking. For downloads, investigate the network, local disk, file sizes, and appropriate transfer concurrency instead.
Is rclone sync safer or faster than rclone copy?
They have different semantics. copy adds or updates destination files, while sync mirrors the source and can delete destination files absent from it. Choose sync only when those deletions are intentional, and test a small directory first.
What should I use on an unattended server?
The Drive backend supports service-account credentials. Configure the account through rclone, grant it access to the required files or shared drives, and protect the credential files. A service account does not automatically have access to a user’s private My Drive data.
The Bottom Line
Set up and verify the remote first, measure where time is spent, and tune only that bottleneck. Use --fast-list for listing-heavy trees, --drive-chunk-size for memory-safe large uploads, and conservative changes to --transfers or --checkers. Drive’s small-file rate limits, host memory, and sync semantics matter as much as raw network speed.
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.
