From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: location@lists.ipfire.org Subject: Re: Next steps of IPFire Location Date: Thu, 19 Nov 2020 13:10:36 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8570268483488201378==" List-Id: --===============8570268483488201378== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I managed to export the database on my IPFire Mini Appliance in about one min= ute: [root(a)fw01 libloc]# time location export --directory=3Dtmp --format=3Dxt_ge= oip real 1m3.423s user 1m1.470s sys 0m1.009s The system was under a little bit of load due to some network activity, but I= am generally quite happy with this. I added some more fine-tuning and could decrease the export time on my Debian= test machine by another 40% to around six seconds. -Michael > On 18 Nov 2020, at 19:26, Michael Tremer wrot= e: >=20 > Hello, >=20 > Since there are now so many people involved in this project, I would like t= o send a little email to report what has happened and what the next steps are= going to be=E2=80=A6 >=20 > I have spent (unfortunately) a lot of time to add the ability that we can = =E2=80=9Cflatten the tree=E2=80=9D when we export it. That means that no netw= ork will overlap with another one and we do not need to care about any orders= of iptables rules being added. >=20 > That was quite a slow process in Python and since IPFire has to run on smal= l hardware it needed to be ported into C. The tree can now be exported in abo= ut 10 seconds on my development box which is running an Intel Xeon E5-2630 pr= ocessor. >=20 > I hope that we can reach acceptable times of only a few minutes on the slow= est systems and way under a minute on an average system. To find out about th= at, I need you help: >=20 > I just pushed all changes into the next tree and would everyone who can to = install that and report how long this command runs: >=20 > mkdir tmp > time location export --directory=3Dtmp --format=3Dxt_geoip >=20 > It would also be great if you could all check the output if this is still c= orrect. I have done what I could, but I want to have an extra pair of eyes if= possible. >=20 > If this works well, and no more regressions are being found, I will tag thi= s release and we will close Core Update 153. >=20 > We will then roll out all recent changes that make the database better, but= had to be held back because the tree needs to be flattened for most use-case= s now. All older clients will then no longer receive an updated database any = more. >=20 > Happy testing. >=20 > Best, > -Michael --===============8570268483488201378==--