Download Sites -- mirroring & load distribution

For examle :I have 5.000 customers. I want to upload a new version of my program about 3 mb.I have 3 servers for updates.

I want this:some of my customers can download updates from server-1some of them can download updates from server-2and the other from server-3

Is there any way in a project file.

I see the "Download Sites" section.I tried to enter 4 download sites. But WyUpdate always download the update files where it be found.

1 - file://C:/Updates/%file% (there is no update files here)2 - http://www.myserver1.com/%file% (there are update files here)3 - http://www.myserver2.com/%file% (there are update files here)4 - http://www.myserver3.com/%file% (there are update files here)

WyUpdate always use second (http://www.myserver1.com/%file%) entry for downloading.

Hey Erol,

wyBuild can't do that because wyUpdate can't detect the load on your servers. For instance, we could write it so that wyUpdate randomly chose a site from the list of available sites, but this wouldn't solve the problem because wyUpdate can't know which of your servers is more heavily loaded than the others. The alternative sites are used as backup sites if the earlier sites in the list fail (for whatever the reason).

What you're looking for is either load balancing or a content delivery network. This has to be done on your servers. That is, add a single site to the "download sites" and you handle load distribution on your servers.

I see.But your suggestion is very complex for me. ( and I think too for the others) Before using wybuild I solved the my problem by random server select. (Yes my problem is solved by this way 🙂 )I suggest this solution to wybuild. Yes it not absolute solution but now there is no any solution in wybuild.

My suggestion is that: There can be group inserts in "Download Sites" section . I mean;

+---> file://C:/Updates/%file% (in first group)|+---> http://www.myserver1.com/%file% (in second group) | http://www.myserver2.com/%file% (in second group)| http://www.myserver3.com/%file% (in second group)| http://www.myserver4.com/%file% (in second group)|+---> http://www.myserver5.com/%file% (in third group) | http://www.myserver6.com/%file% (in third group)

wyupdate must checks a random location in first group. If it hasnt any updates files, and than wyupdate must a random location in second group If it hasnt any updates files, and than wyupdate must a random location in third group.. If it hasnt any updates files, and than wyupdate must a random location in xxxxx I need this and it is enough for me. (Actually I need only two groups and random select) What do you think?

But your suggestion is very complex for me. ( and I think too for the others)

Well, load balancing and content delivery networks (CDNs) are complex subjects. But once load issue actually become a problem for you, you should look into it. There are lots of companies that simplify CDNs to a single click operation.

Why we're not going to do "choose a random site" type "load balancing".

I think I understated the problem in my response, so let me clarify: the "chose a random site and pray for the best" type load balancing is extremely bad. It doesn't do any real load balancing - it's a placebo. You'd be better off crossing your fingers and hoping your users don't all check at the same time.

By the way, the example you gave isn't a terribly large load. In fact, it's rather small - any cheap server would be able to handle that without much stress at all. It would only be a problem if all your 5000 users tried to reach your site at the exact same second. But, if your server were configured correctly, then even this wouldn't be a huge problem. You server might have to let a few of those connections time out, but they'll be able to try again when your server could handle it.

But I think you're putting the cart before the horse. You only need to worry about "scaling" and CDNs around the time you actually need them.

Reply
Discard post