Re: The end of ewi546

>>
>> But when we release new version bandwidth usage is very big -
>> for example OpenZaurus 3.5.4.1 took about 14GB in first days
>> after release. We have to think how to solve it as we do not
>> have mirrors without transfer limits now.
>>
>> One of solutions is moving OpenZaurus to LinuxToGo but it
>> would need getting new machine to LTG project so we have to
>> collect money. That will also mean moving website from
>> SourceForge so it will work faster.
>>
>> Any thoughts/commments/suggestions?

Why not set up a load-sharing/distribution system to distribute  
requests to different mirrors
during the peak periods of an initial release?
We don't have enough bandwidth here to take the load for all the OZ  
community, but we could certainly
take a slice, esp. if others do the same.

'dillo

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV