Do any organizations have information regarding the file browser performance and how it plays/works with file systems (Vast, Lustre)? Our institution has some interest from the storage teams about how other institutions are seeing users engage with this part of the site, if it causes any IO strain, etc. If you have any comments to share, I appreciate it.
Kanin:
I’m not sure what you mean by ‘file browser performance’?
Here are OSC, a super-majority of our ~8,000 clients regularly utilize Open OnDemand for all their interactions with our systems. We have many many petabytes of both NFS and GPFS based storage and I’ve never heard any issues / concerns about IO strain.
In fact, our official recommendation to clients is that if they are working with files up to about ~8GB in size, to just utilize Open OnDemand. I’ve personally uploaded / downloaded files that big on our production systems with no issues and very quick throughput (a few minutes at most).
I’m not entirely sure what was meant either, but I think you’ve covered a large area. “How large of files can safely be downloaded” and no noticeable IO constrain were some of my own questions. The only other question I can come up with is if there’s a limit to the number of files displayed to a user, files downloaded concurrently, or other web operations that might cause less performant browser behavior (page lag, excessive load times, etc), which I would imagine you wouldn’t see much of since OOD is a pretty lightweight application.