[members-discuss] RIPE DB NRTM access.
Pawel Tyll ptyll at nitronet.pl
Sat Jan 7 23:18:19 CET 2012
Hi Andrea, > maybe a simple rsync server would do the job for you and for everyone > else with similar needs (described as "I need a periodic update but I > don't really need a realtime one"). It isn't a "realtime" one, it's a simple polling mechanism that hits the whois server every 30 mins (by default), supplies local serial number and requests changes between local sn and current RIPE sn. Nothing realtime about it. Downloading 200MB file isn't a problem. It takes less than a minute. Real trouble is restarting irrd - with 3GB database (which ripe.db.gz unpacks to), it takes about 20 mins on the machine I want to use for this purpose, also creating unnecessary load. > At our site we mirror a few terabytes of data (genomic repositories) > via rsync without even noticing an impact of bandwidth usage (as long > as only a small part of those big files changes every day). Like I said, file size isn't a problem. Unnecessary processing required due to irrd restart is a problem. --Pawel.