[RADIATOR] What TPS are you getitng on your radiator
cihangir sinan koca
csinankoca at gmail.com
Tue Dec 17 07:29:34 UTC 2019
Hi Heikki,
Thanks for your answer. Due to a routing issue on network, one database
query was taking 100ms for each Radiator (we got 2) After we fix the issue,
now a query takes 2 ms for the first one, for second one its 20ms. So TPS
is much better now.
For the second one, which is taking 20ms, we will consider to use Farmsize
command.
Thanks
Best Regards
Heikki Vatiainen <hvn at open.com.au>, 13 Ara 2019 Cum, 16:36 tarihinde şunu
yazdı:
> On 10/12/2019 15.52, cihangir sinan koca wrote:
>
> > What we are facing is, servers are unable to process more packet than
> > 50-60 TPS. After i while its not writing the problem in logs, its not
> > answering to any packet.
> >
> > Is it expected ? Or are we doing something wrong ?
>
> I'd say it's possible and possibly not, respectively :)
>
> Database access is synchronous. If DB takes a long time to respond, it
> will lower TPS rate for a single Radiator instance. To fix this, you
> take a look at FarmSize parameter to increase the number of instances to
> make processing parallel.
>
> FarmSize works with protocols such as PAP, MSCHAP and its derivatives
> and RADIUS accounting. With EAP you need to do more because it uses
> multiple messages for each authentication and the related messages must
> be processed by the same instance.
>
> To summarise: there can be many reasons why TPS rate is low. Sometimes
> indexing on the DB side helps a lot, sometimes there are DNS requests
> for each query or it may be a number of different things such as a
> complex configuration that consults 3 databases for each request. You
> should also check that you are not using debug logging while trying to
> test performance.
>
> I would look at DB indexing and logs on the DB side and Radiator
> configuration log level and complexity on Radiator side.
>
> Thanks,
> Heikki
>
> --
> Heikki Vatiainen <hvn at open.com.au>
>
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory,
> EAP, TLS, TTLS, PEAP, WiMAX, RSA, Vasco, Yubikey, HOTP, TOTP,
> DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, etc.
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open.com.au/pipermail/radiator/attachments/20191217/f83032d4/attachment.html>
More information about the radiator
mailing list