Skip to main content

OSX Photo is taking too long to sync

I've complained about my wife's OSX machine in the recent past. This issue is that when I enable iCloud sync my home network slows to a crawl. The only evidence that I have for the network failure is congestion at the router. At the time my network was rated at 5MB/50MB (up/dn).

And with a little luck my ISP upgraded me to 10MB/100MB today. Since my photos never completed the sync I restarted the process today. As it turns out I watched a national news article about computer ransom-ware last night and I needed to get the backup started again.

The increase in bandwidth did not really fix things but it did redirect my focus.

  • I might have failed to notice that Photo, backblaze and G+ were all running at the same time. That's not a solid practice.
  • Photo's sync seems to use a shared OSX proxy so that it can monitor or shape the network usage, however, the end result seems to have been complete network saturation.
  • Uploading files at WiFi speeds or even 100MG should not be taking to the CPU. And at the same time the fan was going crazy the "monitor" indicated that there was no network usage. When I switched over to CPU is seems that a codec was using all available CPU.
Well my network issue has not been resolved except that the interruptions per upload are fewer. The problem, however, is that while my wife has been taking new pictures we are not safe.

UPDATE 2016-04-25:  When I connected my MacBook to a wired network my sync seemed to make progress and only mildly disturbed the other systems in my network. I'm not crazy with the notion that a single wireless device could crash the entire LAN.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…