This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
- Previous message (by thread): [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
- Next message (by thread): [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Tue Nov 10 11:27:17 CET 2015
On 10/11/2015 10:18, Stephan Wolf wrote: > ANCHOR as an VM would really make sense. > What do you think about this ? it depends how the hypervisor is managed. I've seen some completely overloaded hypervisors where the VM performance is terrible. At least with the hardware probe, the RIPE NCC controls everything down to the hardware, which makes it more predictable to manage, which means better results. Nick
- Previous message (by thread): [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
- Next message (by thread): [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]