aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Chu-Carroll <>
Subject Possible Vagrant configuration change
Date Sun, 02 Feb 2014 02:06:25 GMT

I've been working on getting together an and-to-end test for open-source
Aurora. In order to get it working with a realistic scenario including
multiple task instances, I've modified the vagrant configuration to launch
to mesos slaves, each of which believes that it has 4cpus to allocate. I'd
like to make this two-slave setup the default vagrant configuration.

On my work laptop (Macbook Pro, 4 cores, 8GB memory), it's
indistinguishable from running with just one slave - there's no visible
impact on the performance of other tasks, and running little benchmarks on
my laptop show no statistically meaningful variation between the 1 and 2
slave configs when no tasks are running on the slaves.  I suspect that with
less memory, there would be more performance impact, but I can't measure

Does anyone object to this change?  (If so, I'll put this as a new
Vagrantfile in the directory containing the end-to-end tests. But I'd
really prefer to have a single canonical vagrant test/demonstration



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message