You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all I just started using juicefs in GCP. So far it works great and I really appreciate your work. I feel this piece of software is well architected and well made.
It seems though commands like git status is slow with juicefs due to a lot of lstat() calls to the metadata server. Here is an idea:
how about have a bit in the metadata server for the version of of the last change? If the client detected that it has the latest version of the FS metadata, it can skip getting all the info per inode? This could significantly speed up lstat() in the common case when nothing has changed?
Also, on GCP, I noticed juicefs sync is behavior strangely. When I sync a file like:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
First of all I just started using juicefs in GCP. So far it works great and I really appreciate your work. I feel this piece of software is well architected and well made.
It seems though commands like git status is slow with juicefs due to a lot of lstat() calls to the metadata server. Here is an idea:
Also, on GCP, I noticed juicefs sync is behavior strangely. When I sync a file like:
juicefs sync gs://bucket_name/dir_name /jfs/dir_name
2 strange things feels like bugs:
I don't know where does the suffix "-16" came from really.
Beta Was this translation helpful? Give feedback.
All reactions