Hi Antonio - I would need to see your configuration file(s) before making suggestions.
If you send copies to me directly I will take a look. regards Hugh > On 24 Sep 2015, at 18:10, António Mendes <antonio.men...@wit-software.com> > wrote: > > Hi Hugh, thanks for your answer. > > The "father" process is consuming too much CPU due to the amount of requests, > it's perfectly normal because we have a huge amount of clients. The > Radiator's performance it's not a problem. > We need to move forward because we see that the hardware it's underused(one > CPU core reaches several time 100% of use but the others are unused). To > avoid this problem and make use of all cores available we take a look of > "Farmsize" feature, but like I said we are a bit worried about problems that > could arise, like concurrency problems. So my question is if there are known > problems in use the Farmsize, or do you advise to upgrade the configuration > in another way. > > Please note that we are thinking to use the Farmsize in accounting process, > so the known authentication problems will not be a problem for us. > > Best regards, > António Mendes > > WIT Software | Software Engineer > > This email was sent under WIT Software's Confidentiality Policy > > Às 07:38 de 24-09-2015, Hugh Irvine escreveu: >> Hello Antonio - >> >> I am curious to know why your “father” process is taking so much time? >> >> Have you checked a trace 4 debug with LogMicroseconds enabled to see what >> exactly is taking the time? >> >> If you send me a copy of your configuration file(s) directly, I will take a >> look and try to make some suggestions. >> >> FarmSize can be used in some situations, but it can cause problems in other >> situations. >> >> regards >> >> Hugh >> >> >> >>> On 24 Sep 2015, at 00:40, António Mendes <antonio.men...@wit-software.com> >>> wrote: >>> >>> Hello all, >>> >>> We are running a scenario with an instance acting as a father and >>> forwarding the traffic for children processes according to some parameters >>> in request. We done that changing the init script and starting several >>> instances of radiator(each one in a different port). >>> >>> We are noticing that the father process are consuming too much processing >>> resources and is only using one core, we would like to change this >>> configuration to allow the distribution of load for all CPU cores available >>> in the server and to do that we are thinking to use "FarmSize" and create >>> several instances of father process. >>> >>> Do you see any problem with this new approach(I'm a little bit worried >>> about the write concurrency of log files)? Do you have any concern or >>> recommendations? >>> >>> >>> Thanks >>> -- >>> António Mendes >>> >>> WIT Software | Software Engineer >>> >>> This email was sent under WIT Software's Confidentiality Policy >>> >>> _______________________________________________ >>> radiator mailing list >>> >>> radiator@open.com.au >>> http://www.open.com.au/mailman/listinfo/radiator >> >> -- >> >> Hugh Irvine >> >> h...@open.com.au >> >> >> Radiator: the most portable, flexible and configurable RADIUS server >> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, >> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, >> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, >> DIAMETER, SIM, etc. >> Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc. >> >> > -- Hugh Irvine h...@open.com.au Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER, SIM, etc. Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
