(RADIATOR) Radiator and Mysql under load

[DUFOUR Geoffrey]

I don't know much about InnoDB.

Does it require a commercial license ?

It seems InnoDB is enabled by default in Mysql 4.0. Correct ?

Regards.

Geoffrey


-----Message d'origine-----
De : Matthew Trout [mailto:MatthewTrout at businessserve.co.uk] 
Envoyé : mercredi 20 août 2003 10:29
À : 'Hugh Irvine'; DUFOUR Geoffrey
Cc : radiator at open.com.au
Objet : RE: (RADIATOR) Radiator and Mysql under load

I'd also *strongly* recommend using InnoDB for the MySQL table handler - I
sincerely doubt MyISAM will perform well in the environment you're looking
at.

Plus make full use of mysql's 'EXPLAIN' keyword to optimise your table
indexes based on the queries radiator's performing.

> -----Original Message-----
> From: Hugh Irvine [mailto:hugh at open.com.au] 
> Sent: 18 August 2003 23:49
> To: DUFOUR Geoffrey
> Cc: radiator at open.com.au
> Subject: Re: (RADIATOR) Radiator and Mysql under load
> 
> 
> 
> Hello Geoffrey -
> 
> You shouldn't have any problems with the numbers you indicate below.
> 
> In answer to your questions:
> 
> 1. I would say that most of our customers use MySQL, with both Oracle 
> and MSSQL used less often.
> 
> 2. At startup the Radiator configuration file is parsed and a variety 
> of memory structures are built including a list of Realms. 
> 1000 Realms 
> will not use much memory at all - less than a megabyte I would say.
> 
> BTW - if the Realms are being used for proxying, you might 
> consider the 
> AuthBy SQLRADIUS clause as an alternative which allows you to manage 
> the list of Realms in the database as well. See section 6.45 in the 
> Radiator 3.6 reference manual ("doc/ref.html").
> 
> Of course you should also set up a test environment so you 
> can see how 
> your configuration performs.
> 
> regards
> 
> Hugh
> 
> 
> On Tuesday, Aug 19, 2003, at 01:16 Australia/Melbourne, 
> DUFOUR Geoffrey 
> wrote:
> 
> > Hello,
> >  
> > We plan to run RADIATOR on RH Linux and authenticate users from a 
> > mysql database (accounting information will be stored in the same 
> > database). We have to work with a data model that allows us 
> to handle 
> > "group attributes" (reply and check),  "user attributes" (reply and 
> > check), and a few other things, meaning that the AuthSelect 
> query will 
> > deal with several tables.
> >  
> > We should have up to 50.000 users in the database and 1000 
> realms in 
> > the config file (1500000 CDRs a month).
> >  
> > 1st question : Knowing all this, do you see any problems running 
> > RADIATOR with mysql (performance problems, ...). It seems a lot of 
> > people are working with MSSQL or Oracle databases to authenticate 
> > users.
> >  
> > 2nd question : Is it a problem for RADIATOR to handle a lot 
> of realms, 
> > knowing all the information is kept in memory ?
> >
> > I am concerned about performance.
> >  
> > Thanks for your help.
> >  
> > Regards.
> >  
> > Geoffrey Dufour
> > ===
> > 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.
> >
> >
> 
> NB: have you included a copy of your configuration file (no secrets),
> together with a trace 4 debug showing what is happening?
> 
> -- 
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
> -
> Nets: internetwork inventory and management - graphical, extensible,
> flexible with hardware, software, platform and database independence.
> 
> ===
> 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.
> 
===
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.