file storage shared by matlab clients and workers -凯发k8网页登录
file storage shared by matlab clients and workers
since r2022a
description
filestore
is an object that stores files owned by a specific
job. each entry of the object consists of a file and its corresponding key. when the owning
job is deleted, the filestore
object is deleted as well. use
filestore
to store files from matlab® workers that can be retrieved by matlab clients during the execution of a job (even while the job is still
running).
any matlab process client or worker can write an entry to the
filestore
at any time. any matlab process client or worker can then read this entry from thefilestore
at any time. however, the ordering of operations executed by different processes is not guaranteed.filestore
can be used to return files when a cluster has no shared file system, or to run code that is not concerned about the location of any shared file system.filestore
is not held in system memory, so it can be used to store large results.
creation
the filestore
object is automatically created when you create:
a job on a cluster, which is a object. to create a job, use the , , or function.
a parallel pool of process workers on the local machine, which is a object. to create a process pool, use the
parpool
function.a parallel pool of workers on a cluster of machines, which is a object. to create a cluster pool, use the
parpool
function.
you can access the filestore
object on a worker by using the function. you can then retrieve the
filestore
object on a client by using the filestore
property that is associated with the job or the parallel pool. for example, see run batch job and retrieve files from workers.
properties
object functions
determine if valuestore or filestore object
contains keys | |
return all keys of valuestore or filestore
object | |
copy files from local file system to filestore
object | |
copy files from filestore object to local file
system | |
remove entries from valuestore or filestore
object |
examples
limitations
when using
parallel.cluster.generic
clusters with'hassharedfilesystem'
set tofalse
, the visibility of modifications made tofilestore
while a job is running depends on your specific implementation. without additional synchronization between the matlab client and workerjobstoragelocation
, changes might only be visible once the job has completed.
version history
introduced in r2022a
see also
| | | |