-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offload import process #26
Comments
You can import that with more powerful machine and then change the home directory once you move it to power efficient server. see https://docs.lomorage.com/docs/Usage/lomorage-client/#reset-users-backup-home-directory-and-backup-directory |
Ok but I thought using another machine but with the same home directory (home directory is on a NAS). |
should be fine, but I guess remote mount the NAS as Homer directory is more
likely to be the bottleneck than CPU?
…On Fri, Aug 5, 2022 at 3:16 PM darrepac ***@***.***> wrote:
Ok but I thought using another machine but with the same home directory
(home directory is on a NAS).
There will be no conflict having 2 lomo instance on 2 different machines
pointing on to the same home directory?
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIA466FVRR4EMDH3WPYXX3VXWHCHANCNFSM55L3VSSQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
That’s why I am currently running lomorage on my NAS… but seeing that after 15days, import is still not finished, I guess CPU is more the bottleneck (and videos) I don’t know if the windows executable as an import with « no move » option. If yes, I think the problem will be how to replace the absolute path of assets in the database (the one from windows instance would be different than the one from NAS instance) |
One option is to use Linux machine or VM to import, and mount it with the same path you are going to use later. |
👍
… Le 7 août 2022 à 04:53, Jiantao Fu ***@***.***> a écrit :
One option is to use Linux machine or VM to import, and mount it with the same path you are going to use later.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
@darrepac , to speed up import process, now "--no-video" is added to skip video import, see https://docs.lomorage.com/docs/Usage/lomorage-client/#import-from-one-existing-folders |
close it now, feel free to reopen if it still happens. |
Hi,
Is there a mean to offload the import process?
I have a big set of pictures and video that take age to import (due to transcoding and my server processor not being the latest one)
For doing so I am doing an import with no move option in the container running on my server.
Is there a mean to run this import from a more powerful machine yet filling the database in the container server? (I have a windows desktop PC which is more powerful)
The text was updated successfully, but these errors were encountered: