I tried the rust-http's comparison with go from here.
https://github.com/chris-morgan/rust-http/tree/master/comparisons
Using the default code, which I guess uses 1:1 scheduling, rust falls
behind go when concurrency goes greater than the number of cores (4). I
guess this is to be expected as
Hi,
This piece of code,
#![feature(phase)]
#[phase(plugin)]
extern crate green;
use std::io::timer;
use std::task::TaskBuilder;
green_start!(main)
fn main() {
for _ in range(0, 1i) {
TaskBuilder::new().stack_size(20*1024).spawn(proc() {
timer::sleep(2)
});
}
}
fails with,
task
get a 1K stack which the task
can run in.
On Wed, Jul 9, 2014 at 8:13 AM, Chandru chandru...@gmail.com wrote:
Hi,
This piece of code,
#![feature(phase)]
#[phase(plugin)]
extern crate green;
use std::io::timer;
use std::task::TaskBuilder;
green_start!(main)
fn main
