Service Availability Estimation vs Service Discovery

I never got belief in this that computing time to be devoted in service
availability estimation rather than service discovery. A fact tells latency/overhead in 10 bytes of network communication is equal to 100000 CPU cycles. Huhh!!! Big figures, but look at the overhead involved in all this estimation if your prediction goes false, after all algorithms (Linear scaling or Bin) works on past records of service availability or service demise.

A good concept to take from service availability estimation is a fuzzy logic crieteria to compute device availability scale.