File Reader over a Network, Speed issue.

When I open up a definition that has multiple files being read from a network location (using file reader), it takes an extremely long time for the definition to load.

The wait time is a few minutes. The same definition reading files off of my local HD will load up at normal speed (usually a few seconds). Once it the file finally loads, there are no problems. It is just the initial load time.

I am only reading txt files containing 1-2 lines with some numbers. One definition may have about 4-5 file readers for different files. My intent was to set up a few key txt files to contain shared parameters for a team working in different definitions.

Our office network is generally pretty speedy. We are used to pushing large files to the network with little wait time (Saving to a central Revit file, for example).

Has anyone else encountered this problem? Is it the file reader? Something I am overlooking on my network?

Replies to This Discussion

Permalink Reply by David Rutten on July 15, 2011 at 2:58am

Hi Nathan,

I wonder how fast loading is if you do it straight from a VB/C# component. Create a new VB component, remove the "y" input, rename the "x" to "path" and give it a String type-hint. Then double click the VB component and type the following in the RunScript function:

A = System.IO.File.ReadAllLines(path)

Of course you'll need to supply a proper filepath as a string as well.

This takes roughly 5ms on a ~200 line file loaded from local disk. I don't have a network to test this on at home though.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS