• Replies 2 replies
  • Subscribers 60 subscribers
  • Views 3608 views
  • Users 0 members are here

DFT, Caching and Riverbed - Oh My!

Scott Soper
Offline

You know, ever since ProjectWise V8i changed the game (for the better) with file compression and DFT, it's altered the way I look at pre-V8i methods of file transfer enhancements like remote file caching servers and Riverbed appliances.  Between some of the conversations that have populated this forum and independent discussions, there's been a lot of time and effort spent (in my little world anyway) looking at bits and pieces of the issue.  Wouldn't it be great if someone gathered together all of this into a single document or presentation?

It might go something like this:

Begin with a review of Bentley's documentation on DFT practices - when you should run it, when you should turn it off.  Be sure to include network speed considerations.

Next  look at remote caching servers.  Notice I use the term "remote" caching servers, to delineate them from "Caching" servers, which used to be appropriately called "file" servers and hold the "master" set of files.  I think I'll keep complaining about this confusing terminology until Bentley relents...  Anyway, a discussion of when workflow and network speeds determine if remote caching servers should be considered.

Finally, when is it time to look into Riverbed appliances - in conjunction with remote caching servers - without remote caching servers.  What kind of transfer speed increases you can expect for your investment - that kind of thing.

I think most of this information is out there, I would just like to see it consolidated into a single source so that projects looking at transfer speed issues would have one place to go.  There might be someone out there that has already done all this testing in their ProjectWise environment and could define the practices.

Todd Pace, are you out there?

 

Parents
  • Offline

    That's not presentation but I think that might help as well.

    There are two things to consider when using DFT: server CPU power and network speed. DFT algorithm is CPU intensive and in local network sending complete file might be faster than DFT. Using real life examples I have seen only one: file operations were 2 times faster without DFT in local network. However I don't know details: what CPU was used, at what time DFT was tested and etc. This example could be very specific to that environment.

    While we don't offer DFT load test application there is DFT Benchmark Wizard supplied with standard PW installation. I recommend using this tool on real network during work hours to see if DFT helps you or you should disable DFT in local network. I'm pretty sure that DFT is mandatory for remote locations. DFT can be controlled in dmskrnl.cfg. As I have said better CPU on server might change your test results.

    About remote caching servers (officially known as caching gateways). If you have remote team(s) you should seriously consider having caching gateways because of work performance.

    Lastly about Riverbed. As John Schown mentioned (here communities.bentley.com/.../140425.aspx) combination of DFT and Riverbed gives only small benefits.

    I personally don't know much how Riverbeds works internally while some information is available. Based on information I have found out Riverbed optimizations are done at various levels:

    1) MXTCP - this optimization shouldn't have positive or negative effect on DFT. That's general network optimization;

    2) HSTCP (en.wikipedia.org/.../HSTCP) - Again does not look like optimization what could make difference for DFT or no DFT. While in some specific (mostly atypical) situations it might give small benefit for noDFT;

    3) Riverbed does some local caching. In my opinion DFT data sent over network can't be optimized by Riverbed because different users might have files on their system retrieved at different times. Thus noDFT with Riverbed might give better results than DFT without Riverbed. Evaluation must be done very carefully because that really depends on your work style, data formats and your work environment. E.g. if you make frequent changes that are used by your team I would bet on DFT, but if you make one big change per week Riverbed might be better option. But still that depends on how big are your changes, how big are remote teams and if you are using caching gateways. I can actually put it other way round: depending on your choice not to use DFT you might affect your and your team's work style and performance.


    This is a test

Reply
  • Offline

    That's not presentation but I think that might help as well.

    There are two things to consider when using DFT: server CPU power and network speed. DFT algorithm is CPU intensive and in local network sending complete file might be faster than DFT. Using real life examples I have seen only one: file operations were 2 times faster without DFT in local network. However I don't know details: what CPU was used, at what time DFT was tested and etc. This example could be very specific to that environment.

    While we don't offer DFT load test application there is DFT Benchmark Wizard supplied with standard PW installation. I recommend using this tool on real network during work hours to see if DFT helps you or you should disable DFT in local network. I'm pretty sure that DFT is mandatory for remote locations. DFT can be controlled in dmskrnl.cfg. As I have said better CPU on server might change your test results.

    About remote caching servers (officially known as caching gateways). If you have remote team(s) you should seriously consider having caching gateways because of work performance.

    Lastly about Riverbed. As John Schown mentioned (here communities.bentley.com/.../140425.aspx) combination of DFT and Riverbed gives only small benefits.

    I personally don't know much how Riverbeds works internally while some information is available. Based on information I have found out Riverbed optimizations are done at various levels:

    1) MXTCP - this optimization shouldn't have positive or negative effect on DFT. That's general network optimization;

    2) HSTCP (en.wikipedia.org/.../HSTCP) - Again does not look like optimization what could make difference for DFT or no DFT. While in some specific (mostly atypical) situations it might give small benefit for noDFT;

    3) Riverbed does some local caching. In my opinion DFT data sent over network can't be optimized by Riverbed because different users might have files on their system retrieved at different times. Thus noDFT with Riverbed might give better results than DFT without Riverbed. Evaluation must be done very carefully because that really depends on your work style, data formats and your work environment. E.g. if you make frequent changes that are used by your team I would bet on DFT, but if you make one big change per week Riverbed might be better option. But still that depends on how big are your changes, how big are remote teams and if you are using caching gateways. I can actually put it other way round: depending on your choice not to use DFT you might affect your and your team's work style and performance.


    This is a test

Children
No Data

Communities
Support and Services
Training and Learning
Social Media