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: Sun, 22 Nov 2020 21:06:51 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5321887941941402560==" List-Id: --===============5321887941941402560== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Dear All, I have the results now for the location testing on my Intel(R) Celeron(R) CPU= J1900 @ 1.99GHz production box. Stable real=C2=A0=C2=A0=C2=A0 0m37.240s user=C2=A0=C2=A0=C2=A0 0m37.086s sys=C2=A0=C2=A0=C2=A0 0m0.070s Unstable real=C2=A0=C2=A0=C2=A0 0m25.827s user=C2=A0=C2=A0=C2=A0 0m25.568s sys=C2=A0=C2=A0=C2=A0 0m0.123s Regards, Adolf. On 19/11/2020 18:48, Adolf Belka wrote: > 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) Cele= ron(R) CPU J1900 @ 1.99GHz but I have to prepare for that as I will need to r= e-install Core152 after carrying out the test. Will email the results when I = have 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 = minute: >> >> [root(a)fw01 libloc]# time location export --directory=3Dtmp --format=3Dxt= _geoip >> >> real=C2=A0=C2=A0=C2=A0 1m3.423s >> user=C2=A0=C2=A0=C2=A0 1m1.470s >> sys=C2=A0=C2=A0=C2=A0=C2=A0 0m1.009s >> >> The system was under a little bit of load due to some network activity, bu= t I am generally quite happy with this. >> >> I added some more fine-tuning and could decrease the export time on my Deb= ian test machine by another 40% to around six seconds. >> >> -Michael >> >>> On 18 Nov 2020, at 19:26, Michael Tremer wr= ote: >>> >>> 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 a= re 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 net= work will overlap with another one and we do not need to care about any order= s of iptables rules being added. >>> >>> That was quite a slow process in Python and since IPFire has to run on sm= all hardware it needed to be ported into C. The tree can now be exported in a= bout 10 seconds on my development box which is running an Intel Xeon E5-2630 = processor. >>> >>> I hope that we can reach acceptable times of only a few minutes on the sl= owest systems and way under a minute on an average system. To find out about = that, I need you help: >>> >>> I just pushed all changes into the next tree and would everyone who can t= o install that and report how long this command runs: >>> >>> =C2=A0 mkdir tmp >>> =C2=A0 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 = if possible. >>> >>> If this works well, and no more regressions are being found, I will tag t= his release and we will close Core Update 153. >>> >>> We will then roll out all recent changes that make the database better, b= ut had to be held back because the tree needs to be flattened for most use-ca= ses now. All older clients will then no longer receive an updated database an= y more. >>> >>> Happy testing. >>> >>> Best, >>> -Michael >> --===============5321887941941402560==--