> Yes. This is very useful if you have poor bandwidth but fast disks.
> Reading/writing temp files over NFS can be a huge bottleneck.
So in theory I could and probably should configure
org.opencastproject.storage.dir to point to local storage right?
> We put everything over NFS.
We have the capability to provision different NFS mounts with different
tiers of storage. Some of it fast and expensive. Some of it slow and
cheap. My question is, what would be the best way to take advantage of
this? For example, perhaps the inbox or download and streaming
distribution (we don't expect a lot of traffic for testing) directories
could be on slower cheaper storage. Would this make sense or are there
other hidden considerations to be aware of?
Looking at Jaime's link:
http://opencast.jira.com/wiki/display/MH/SAMPLE+Customization
What is the working file repository?
What is the shared workspace?
Also that post makes no note of some of the options you said you set,
namely:
org.opencastproject.workflow.solr.dir=${org.opencastproject.storage.dir}/workflow
org.opencastproject.file.repo.path=${org.opencastproject.storage.dir}/files
What do these do? What other storage things can be specified? What do
they do?
This question sort of merges with the other question that Alex raised
about storage in general. That is, is there any clear documentation for
the storage directories that would enable adopters to make decisions on
how much/fast/where storage should be allocated?
--
Jon
On 9/12/12 1:20 PM, Christopher Brooks wrote:
Jonathan,
Is there any performance to be gained by having the workers pull
files off of shared shared storage onto local storage, perform the
workflows, and then putting the results back onto shared storage? Is
this configuration even possible or desirable?
Yes. This is very useful if you have poor bandwidth but fast disks.
Reading/writing temp files over NFS can be a huge bottleneck.
Also are you recommending different tiers of storage for the
different settings? For example, should the workspace mounts be on a
separate mount with faster storage?
We put everything over NFS. So our workers config looks like:
org.opencastproject.storage.dir=/data/opencast
org.opencastproject.file.repo.path=${org.opencastproject.storage.dir}/files
#org.opencastproject.file.repo.url=${org.opencastproject.admin.ui.url}
org.opencastproject.workspace.rootdir=${org.opencastproject.storage.dir}/workspace
org.opencastproject.workflow.solr.dir=${org.opencastproject.storage.dir}/workflow
So all of our workers share files over NFS. Our workspace directory
then looks something like:
http_mhadmin.usask.ca_8080
http_mhengage1.usask.ca_8080
http_mhworker2.usask.ca_8080
http_mhworker3.usask.ca_8080
http_mhworker4.usask.ca_8080
Since all of our machines share the workspace mount.
Having this on local storage would likely be faster, but since we're
using VMs for everything we don't have local storage options.
Chris
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
