From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Next steps of IPFire Location Date: Thu, 19 Nov 2020 18:48:56 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5385403935502295804==" List-Id: --===============5385403935502295804== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I have tested it out on my IPFire virtual machine test bed. I got between 4.8 and 5 secs. The computer is an i5-8400 CPU @ 2.80GHz I will also be testing it out on my production box which is a Intel(R) Celero= n(R) CPU J1900 @ 1.99GHz but I have to prepare for that as I will need to re-= install Core152 after carrying out the test. Will email the results when I ha= ve them. Regards, Adolf. On 19/11/2020 14:10, Michael Tremer wrote: > I managed to export the database on my IPFire Mini Appliance in about one m= inute: >=20 > [root(a)fw01 libloc]# time location export --directory=3Dtmp --format=3Dxt_= geoip >=20 > real 1m3.423s > user 1m1.470s > sys 0m1.009s >=20 > The system was under a little bit of load due to some network activity, but= I am generally quite happy with this. >=20 > I added some more fine-tuning and could decrease the export time on my Debi= an test machine by another 40% to around six seconds. >=20 > -Michael >=20 >> On 18 Nov 2020, at 19:26, Michael Tremer wro= te: >> >> Hello, >> >> Since there are now so many people involved in this project, I would like = to send a little email to report what has happened and what the next steps ar= e going to be=E2=80=A6 >> >> 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. >> >> That was quite a slow process in Python and since IPFire has to run on sma= ll hardware it needed to be ported into C. The tree can now be exported in ab= out 10 seconds on my development box which is running an Intel Xeon E5-2630 p= rocessor. >> >> I hope that we can reach acceptable times of only a few minutes on the slo= west systems and way under a minute on an average system. To find out about t= hat, I need you help: >> >> I just pushed all changes into the next tree and would everyone who can to= install that and report how long this command runs: >> >> mkdir tmp >> time location export --directory=3Dtmp --format=3Dxt_geoip >> >> It would also be great if you could all check the output if this is still = correct. I have done what I could, but I want to have an extra pair of eyes i= f possible. >> >> If this works well, and no more regressions are being found, I will tag th= is release and we will close Core Update 153. >> >> We will then roll out all recent changes that make the database better, bu= t had to be held back because the tree needs to be flattened for most use-cas= es now. All older clients will then no longer receive an updated database any= more. >> >> Happy testing. >> >> Best, >> -Michael >=20 --===============5385403935502295804==--