(RADIATOR) Performance and Tuning.

[Dave Kitabjian]

Hey there,

Besides what Hugh said, here are a couple notes:

1) One of the biggest bangs for the buck in tuning Radiator is to split
the server into 2 servers (2 perl processes): one for Authentication and
the other for Accounting, running side by side on the same box. This
effectively gives you multithreading. And I think each process gets its
own TCP buffer, so you effectively double the number of requests that
buffer before being dropped. Even more importantly, since Auth requests
are typically more critical than Acct requests, while the latter are
typically slower to process, this isolation almost guarantees that no
Auth requests will drop.

2) Let's see your Handler clauses. I can almost guarantee that we can
consolidate them down to a smaller set by using clever perl regexps and
other features of Radiator that encourage modularity. 

Dave

> -----Original Message-----
> From: Julio Cesar Pinto [mailto:jc at ifxcorp.com]
> Sent: Thursday, September 09, 2004 6:59 PM
> To: radiator at open.com.au
> Subject: (RADIATOR) Performance and Tuning.
> 
> At the moment I have aprox 200 session current, and our configuration
> have aprox 350 Handler clauses, at the moment we have in some nases
the
> error radius client timeout, we are sure that we don't have problems
> with networking because we don't lose packets icmp in the same moment
> that we receive a timeout.
> We store all accounting packets in an oracle database.
> 
> So, my question is, we are reaching the capacity of radiator.
> 
> Please let me know.
> 
> Thanks in advance,
> 
> JC.


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.