sanesec.jessen.ch - when and how to synchronise?

Main | Statistics | Rsync timing

If you are looking to run a regular rsync of the sanesecurity data, take a look at these stats to plan for the best, respectively the fastest service. During Juli, August, September and October 2016, the number of clients per minute looked like this:

Requests per minute on average over a month.

I believe it is fairly clear from this chart that:

To pick an optimum time for your rsync, take a look at this map of the minutes:

00010203040506070809
10111213141516171819
20212223242526272829
30313233343536373839
40414243444546474849
50515253545556575859

Recommendation for a 5-minute interval synchronisation

Avoid the crowds; skip the exact 0,5,10,15 stops, and delay it by 1-2-3-4 minutes to 1,6,11,16,21 / 2,7,12,17,22 / 3,8,13,18,23 etc.

Recommendation for an hourly synchronisation

Avoid the rush minutes of 22, 46-54 and the 5-minute peaks; pick any of these minutes instead - 56,57,58,59,26,27,28,29,11,12,13,14,31,32,33,34. Maybe also use the RANDOM_DELAY variable in crontab.

How not to invoke rsync

Try to avoid doing multiple individual requests, one per file. Instead do all the files you want in one request. Doing multiple individual requests one after the other is inefficient and only increases the mirror overhead.

Either do one rsync on the entire directory:

rsync <flags> rsync.sanesecurity.net::sanesecurity/ <targetdir>

or do one rsync for all the files you want:

rsync <flags> rsync.sanesecurity.net::"sanesecurity/file1.nnn sanesecurity/file2.nnn sanesecurity/file3.nnn" <targetdir>

By following these recommendations, you help balance the load on the mirrors, thereby enabling better service for everyone, including yourself.

Hosting in Switzerland

All email sent to alfons.aaberg@jessen.ch will be considered to be spam and processed accordingly.