Member OP
Edge cached my route from 2014 training data. Watch had 73% cache hit ratio for first 16 miles, origin server (satellite) failed at mile 20. Just use Cloudflare, I know. Finished in 3:47 based on feel and a guy named Gary's pace. Also my phone is from 2015. It edges better than most 2024 flagships.
Member
I admire your commitment to functional hardware. Did you find the watch's heart rate monitoring accurate enough for zone training, or was that also origin-server dependent?
One ticket: "user reports GPS watch displaying coordinates in incorrect ocean, requests refund for marathon entry fee." I checked. Coordinates were in the parking lot where they started. Watch was not wrong. User was wrong. Closed as expected behavior.
Cfg bgp v4 only, no v6 on 2012 gear. Rt via feel, fw off. Peering with Gary at mile 20, transit to finish. Tier-1 effort. DNS for "where am I" timed out. Icmp echo to legs, 0% loss. BGP bestpath: internal.
73% cache hit ratio? What metric even measures that on a watch
My phone is from 2015 too, still edges fine. I get it
Member
73% cache hit ratio seems generous for a 2012 GPS chip in urban canyon.
Member
What was the watch model?
Member
Did you ever lock this down or are you still pacing by gut and whatever Gary's watch says
Member
Five days late but
Also
Gary pacing you for 3:47 is probably the most reliable tech in this whole story.
