We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!
slashdotmsiriv (922939) writes "For years, developers and researchers have been refining way to scale Internet services to larger and larger capacities. However, racks full of web servers, database replicas, and load balancing switches require a significant up-front investment. For popular sites, where load is consistently high, it is easy to justify this investment; the resources will not be idle. Less popular sites can not justify the expense of large idle capacity.
The burning question is how can a low-traffic garage-innovator site make the transition to high-traffic when the slashdot hordes make that transition without warning?
This article describes the issues and tradeoffs a typical garage innovator encounters when building low-cost, scalable Internet services.
This is a more formal analysis of the problem and solutions discussed here regarding Animoto's sudden need to scale-up.
In addition, the article offers an overview of current state of utility computing (S3, EC2 etc) and of the most common strategies for building scalable Internet services.
Seems that utility computing is the way of the future for scalable network services; it would be nice to know how to make best use of it." top
slashdotmsiriv (922939) writes "Researchers at EPFL showed that architectural trends in the evolution of microprocessors have shifted the dominant source of overhead in TCP receive processing from per-byte operations, such as data copy and checksumming, to the per-packet operations.
Motivated by this trend, they propose two optimizations to receive side TCP processing, Receive Aggregation and Acknowledgment Offload, which reduce its per-packet overhead. These optimizations result in significant improvements in the receive throughput of TCP in native Linux, by 35% in a uniprocessor and 55% in an SMP system.
slashdotmsiriv (922939) writes "Russia has started building the world's first floating nuclear power station. Russian officials view the highly mobile nuclear power plants on ships as a safe way to power remote isolated areas, without the risk of nuclear proliferation. Greenpeace however, strongly disagrees with this approach and
calls it "The most dangerous project that has been launched by the atomic sector in the whole world over the past decade"
Judging by the safety record of reactors in submarines and icebreaking ships, is Greenpeace once again overreacting over nuclear power?
Also, who will have administrative control over those ships, Russia or the hosting country?" top
"Sun will announce today that its Java language, contrary to the prediction of many pundits, will be offered as pure "Free Software" -as Richard Stallman would say "free as in freedom"- under a GPL version two licence.
Ponytailed CEO Jonathan Schwartz will announce the ground-breaking move in a webcast to be held later at 9:30am Pacific Time. Both Java SE -used on desktops — and Java ME — used on mobile phones and PDAs- will be included. The server-side Java, or Java EE will be available both under the GPL version two licence and the same Common Development and Distribution Licence (CDDL) that Sun has used until now.
This is one of the biggest addition of code to the OSS community and apparently represents a dramatic change in Sun's strategy, which up until now
fiercely protected Java as its IP.
With this move, Sun hopes it will attract many coders, which can enrich Java with new characteristics and extend its lifetime, in the face of competitive emerging OSS technologies (python, ruby on rails etc)."