Very Slow Everything with Mega Remote

Help and Support
1

What is the problem you are having with rclone?

Extremely slow speeds with mega, all of a sudden. I've used it in the past for syncing TBs of files. But now just even listing the remote directory is very slow. 25 seconds to just list 7 remote directories seems excessive. Is there something I'm missing?

$ time rclone lsd mega:/ -vv
2023/10/05 21:14:31 DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "lsd" "mega:/" "-vv"]
2023/10/05 21:14:31 DEBUG : Creating backend with remote "mega:/"
2023/10/05 21:14:31 DEBUG : Using config file from "/home/josh/.config/rclone/rclone.conf"
2023/10/05 21:14:57 DEBUG : fs cache: renaming cache item "mega:/" to be canonical "mega:"
  Directory list here
2023/10/05 21:14:57 DEBUG : 10 go routines active

________________________________________________________
Executed in   25.29 secs    fish           external
   usr time    6.42 secs  703.00 micros    6.42 secs
   sys time    1.10 secs  703.00 micros    1.10 secs

Run the command 'rclone version' and share the full output of the command.

$ rclone version
rclone v1.64.0

  • os/version: arch (64 bit)
  • os/kernel: 6.4.4-arch1-1 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.21.1
  • go/linking: dynamic
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

mega

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone lsd mega:

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

$ rclone config redacted
[mega]
type = mega
user = XXX
pass = XXX

A log from the command that you were trying to run with the -vv flag

$ time rclone lsd mega:/ -vv
2023/10/05 21:14:31 DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "lsd" "mega:/" "-vv"]
2023/10/05 21:14:31 DEBUG : Creating backend with remote "mega:/"
2023/10/05 21:14:31 DEBUG : Using config file from "/home/josh/.config/rclone/rclone.conf"
2023/10/05 21:14:57 DEBUG : fs cache: renaming cache item "mega:/" to be canonical "mega:"
  Directory list here
2023/10/05 21:14:57 DEBUG : 10 go routines active

________________________________________________________
Executed in   25.29 secs    fish           external
   usr time    6.42 secs  703.00 micros    6.42 secs
   sys time    1.10 secs  703.00 micros    1.10 secs
2

welcome to the forum,

would have to look at the full debug log, try to see what is going on.

3

How do I get the full debug log? I thought that's what "-vv" was?

I've used rclone to sync over 4TB of data to Mega in the past, always decent performance. I messed the machine up and lost my config file, so my daily sync job quit working for a while. I just got back to fixing it and now it's so slow it's unusable. I tried to do a sync (total 4TB but only a few gigs of changes), and it ran over night and never sync'd a file. It didn't die either, just sat doing nothing. Would love to get this fixed. rclone is way better than Mega's own cmd program.

4

I'm also wondering if the size of content on Mega impacts performance? I created a new free mega account that was empty, and rclone could read and upload quickly. My personal account that I want to use has about 4.5TB of data. I'm not modifying most or all of it, but it seems that just reading the account with that much data is a performance issue.

5

you can combine two programs.

  1. run megacmd cmd in webdav server mode.
  2. point rclone to that webdav server.

rclone for mega does not support ListR, so listings could be slow as compared to other providers
not sure, maybe try --fast-list

to get a deeper look, add --dump=headers

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.