One of our clients with a support contract had performance issues. We tracked this down to inefficient usage of AAA policies. Having tuned the policies the load on our client’s database dropped by a factor of 400 which saved them from an expensive hardware upgrade.
Project description
A customer created the AAA policies for their organization using their in-house expertise. As their user base grew, the customer started to see performance problems. The customer used their existing support contract to obtain our help.
How we solved it
Our approach
By comparing the customer’s requirements to the RADIUS server logs, we determined that the system was overloading the user information database. When we examined the AAA policies that they had written, the cause was clear.
We re-wrote key portions of the policies to add more preconditions on the database queries. We were able to fine-tune the policies so that queries were sent only when strictly necessary, rather than for every request. This solution was accomplished without affecting any other policies on the system.
The results
When the new policies were deployed, the load on the customer’s database dropped by a factor of four hundred (400). This decreased load allowed the customer to stay with their current systems and saved them from an expensive hardware upgrade.
When the customer purchased a support contract from us, they expected to use it to obtain answers to their questions. The additional benefit they saw was that the support contract saved them money.
Need more help?
InkBridge Networks has been at the forefront of network security for over two decades, tackling complex challenges across various protocols and infrastructures. Our team of seasoned experts has encountered and solved nearly every conceivable network security issue. If you're looking for insights from the architects behind some of the internet's most foundational authentication systems, you can request a quote for network security solutions here.
Related Articles
Database design principles for RADIUS systems
Database design is often overlooked as a critical element of a RADIUS ecosystem. In practice, when we work with our clients, we usually spend the bulk of our time optimizing the database architecture. Our time spent on FreeRADIUS is small in comparison. Why? Because the difference between a fast, reliable RADIUS system and a slow, unstable one is almost always the database.
Client Case Study: Performance
A case study on how we redesigned our client’s system to improve the RADIUS server’s database, which had lost performance over time. The database performance was restored, even with ten times the amount of data, and our client did not need to replace any systems.