FS Sending algorithm (or lack thereof).

I've been trying to figure out if Foldershare is using any kind of
intelligent algorithm to schedule the sending of files. A few of us working
on a collaborative little project basically have 3 remote sites with 1 of the
sites (SITE B) having 3 local users. At one of the remote sites (not the one
with 3 local users) , a build is made from the collaborative data and is
generated into a shared FS library.

So basically the one remote site (SITE A) has updated a large number of
files and needs it to propogate to the other sites. Please note that at this
time, no other transfers requests are happening with this library. So FS
decides that SITE A should send the first of N files to 3 different users
(sometimes the 3 local users of SITE B), it then sends the second of N files
to 3 of the 4 users.

It would be great if FS could smart enough to know that the 3 local users of
SITE A were local to each other and only send the file to one of them, and
then they propogate it to the others. If that wasn't something
implementable, a simpler solution might be that if SITE A realizes that it
has queued up multiple files and only send an individual file once until all
of its queued up files can be sent. At that time, hopefully, the other users
at the other sites would share the sending load.

Right now, SITE A usually ends up spending 3X the upload time it would need
to update the other systems.

I couldn't find any description on FS's methodology but I was under the
impression it was suppose to be a distributive syncing system, which it
doesn't really seem to be.

Thanks for hearing me ramble.

Cary

Cary wrote: I agree, that would be nice, but...

Have you tried reducing the number of simultaneous files FS can send?
(More|Settings|Transfers)


richi.
www.richij.com

Hi Richi,

I should have mentioned that I have tried that with limited success. The
positive part is that it tends not to send the same file 3 times all the
time, but still does 2 and occasionally 3 times in succession (the same file
to differerent one after the other). The reason I don't use this exclusively
is (probably my imagination) due to it always choosing the slowest receiving
peer so I'm not using my full upload capacity.

In any case, thanks for you suggestion.

"Richi Jennings" wrote: