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/[email protected]/
[atlas] probe resolution, overhead, or ...?
- Previous message (by thread): [atlas] probe resolution, overhead, or ...?
- Next message (by thread): [atlas] probe resolution, overhead, or ...?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Jun 20 11:29:17 CEST 2012
On 6/20/12 11:04 , Stelios M. wrote: > > > Ping relies heavily on the system's CPU. That is why it is > considered unreliable for measuring when you are pinging CPU loaded > machines/devices. The CPU on the probe is a n ARM7TDMI running at > 55MHz, based on information from this link: > http://www.digi.com/products/wireless-wired-embedded-solutions/solutions-on-module/digi-connect/digiconnectme#specs > > Probes contain a Lantronix Xport Pro, which has a MC68000 compatible processor. Probes are mostly idle, though some jitter is to be expected from interference between measurements. I have to admit that we never investigated the extent of the jitter problem.
- Previous message (by thread): [atlas] probe resolution, overhead, or ...?
- Next message (by thread): [atlas] probe resolution, overhead, or ...?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]