Click here to access our Podcast/Media archive

Listen to Gear6 Podcasts on iTunes!


  • thoughtput (at)
    Drop us a note with your thoughts or comments. Thanks!

« New World View: Dynamic and Persistent Data | Main | Ratcheting Up Global Namespace Performance »

July 26, 2007



Um, if this how most IT operations worked, 1 of 2 things would be true: either we're in the late 80's or someone needs to get fired.

I thought the gear6 caching appliances is primarily for nfs/hpc environments and not cifs-dominated corporate environments or college-bound nfs home directory stuff.


Gary O.


You are correct that Gear6 provides significant value to NFS environments as well as other enterprise application environments where NFS performance is critical. When other protocols are in use, Gear6 coexists by supporting direct-access.

The content for this checklist came from one of our sales engineers who has experience managing large scale NFS and CIFS storage environments in commercial accounts. Unfortunately when it comes to data movement in NFS and CIFS environments the problem has not changed much since the late 80s. Transparent data movement technology is still evolving into an enterprise ready solution.

Regarding protocols, we tend to look at the target environments more based on application and end-user workload. We find that ideal customers rely heavily on shared I/O (many clients accessing a single data set) and that they often involve job scheduling among multiple constituents. Given these characteristics, the impact of moving data can be significant.

Thanks for the comment and hopefully we answered your questions.



The comments to this entry are closed.