by mitchwainer on 8/29/13, 2:17 PM with 7 comments
by ambiate on 8/29/13, 2:35 PM
Edit: Ok, rather than being an arse, some feedback: The IOWait tidbit was interesting and worth the click on its own.
Build times and bandwidth should vary based on usage on the shared host. Run the tests every 3 hours for 2-3 days and use those results.
More interesting information would consist of what your plan of attack will be for scaling with more power/storage/etc. If necessity dictates the need for more, will it be as easy as a few clicks (and $$$$) with DO as compared to Azure/Amazon?
by joshka on 8/29/13, 3:17 PM
My colleagues and I often use client's hardware rather than our own to work on their project. The mono source sounds like a good stress test to guague the pain and implement preventative upgrades early in the piece.
For comparison's sake, `time make` of mono-3.2.1 from tarball on a 2012 Macbook Pro Retina / 2.6GHz / 16 GB RAM / 512 GB SSD returns:
make 583.12s user 77.90s system 98% cpu 11:11.99 total
This seems slow compared to digital ocean. I wonder if there's something I'm not setting. My settings per [1] were: ./configure --prefix=/Users/joshka/Code/mono --enable-nls=no --build=i386-apple-darwin11.2.0
[1]: http://www.mono-project.com/Compiling_Mono_on_OSXby endijs on 8/29/13, 2:39 PM
by pella on 8/29/13, 9:05 PM
and DigitalOcean benchmarks :http://serverbear.com/9806/digitalocean#view-benchmarks
by hemancuso on 8/29/13, 2:38 PM