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
Hi, I come into juicefs when I am looking for a solution to speed up tensorflow task that running on a legacy HPC cluster, whose file system is GPFS. Now we are experiencing terriable IO performance issue to read data from GPFS directly. I think juicefs can solve the issue by using the RAM and local disk as the cache layer of the GPFS.
The problem is the HPC cluster have mulitple user and they put data in their own directory that only user of the same group can access.
Let's said the fs structure is
/gpfs
/user1 # only user1 have rw permission
/user2 # only user2 have rw permission
I hope that I can create a volumn whose storage is set to /gpfs
And when user1 mounts the volumn to his home, for example, to /home/user1/juicefs,
he can only access /home/user1/juicefs/user1 and not allow to access /home/user1/juicefs/user2.
Is it possbile to do this by using JuiceFS?
Besides, I found this in the docuemnt
Local storage is usually only used to help users understand how JuiceFS works and to give users an experience on the basic features of JuiceFS. The created JuiceFS storage cannot be mounted by other clients within the network and can only be used on a single machine.
I am not sure if it is a good idea to use JuiceFs to speed up districuted file system like NFS/GPFS/Lustre. I find in another solution alluxio that clearly supports NFS. I just wondering if juicefs is production ready or just for demo purpose?
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
-
Hi, I come into juicefs when I am looking for a solution to speed up tensorflow task that running on a legacy HPC cluster, whose file system is GPFS. Now we are experiencing terriable IO performance issue to read data from GPFS directly. I think juicefs can solve the issue by using the RAM and local disk as the cache layer of the GPFS.
The problem is the HPC cluster have mulitple user and they put data in their own directory that only user of the same group can access.
Let's said the fs structure is
I hope that I can create a volumn whose storage is set to /gpfs
And when user1 mounts the volumn to his home, for example, to
/home/user1/juicefs
,he can only access
/home/user1/juicefs/user1
and not allow to access/home/user1/juicefs/user2
.Is it possbile to do this by using JuiceFS?
Besides, I found this in the docuemnt
I am not sure if it is a good idea to use JuiceFs to speed up districuted file system like NFS/GPFS/Lustre. I find in another solution
alluxio
that clearly supports NFS. I just wondering if juicefs is production ready or just for demo purpose?Beta Was this translation helpful? Give feedback.
All reactions