(RADIATOR) MySQL Oracle
Hi All, Currently, we have more than 50 NAS client which is authenticate to our Radiator on Redhat, using local MySQL database. We have tested to change the database using Oracle, running on other Sun machine and 3 NAS client, and works fine. But when we try to make 50 NAS client authenticated, Radiator (very slow) and stop respond with client, but Radiator not die or hang. After we kill and run Radiator again, then it's respond again and after 15 minutes it stop responding again. And we have try to run Radiator on Sun machine, and sending the accounting to other Sun machine which is running Oracle, and it's act the same. We've plan to change the database from MySQL to Oracle, because MySQL have locking mechanism, so when we try to query some accounting, the user could not login because the database is locked. My question is: 1. is anyone have this problem before and have solution for this situation? 2. it is safe to run MySQL without lock option? 3. how much is the maximum client should Radiator handled, for the best performance using Oracle database? 4. it is better to run Radiator on the same machine with Oracle server on Sun or should be separated? TIA Rgds, Fastest === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) MySQL Oracle
On Tue, 8 Feb 2000, Yang Tercepat wrote: My question is: 1. is anyone have this problem before and have solution for this situation? 2. it is safe to run MySQL without lock option? 3. how much is the maximum client should Radiator handled, for the best performance using Oracle database? 4. it is better to run Radiator on the same machine with Oracle server on Sun or should be separated? First of all it is my understanding that MySQL is significantly faster than Oracle, which is probably why your Oracle server is having trouble with the volume. With that said, the way that we handle the problem is that we have a temporary table to all of the login records are written to. Then a seperate process copies all of the records from the temporary table to the permanent table. This process happens every 60 seconds so there are usually less than 200 records in the temporary table at any time. All queries are done on the permanent table so radius is never locked out from writing records. The most important thing to do is run at least 2 DB servers. One which handle authentication and one which handle accounting. In addition run two radius processes, on for authentication and one for accounting. This way your accounting records will never hold up the radius server from authenticating anyone. In actual practice I think that you will find that your RAS will start having problems as your accounting backs up, even if authentication is going through. You will also start to see a lot of duplicates. Steve --- Steve Roderick ProAxis Communications, Inc. [EMAIL PROTECTED] Internet Access Provider (541) 757-0248 === Archive at http://www.thesite.com.au/~radiator/ To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
