1 / 8

HELGA - A Call Load Generator

This presentation details the development of a load generator for testing a 1xEV-DO Radio Network Controller (RNC) using Erlang versus a non-Erlang solution based on Perl. Key points include the need for concurrency in call simulations, distributed architecture, and efficient report generation. The advantages of the Erlang solution are highlighted, including inherent concurrency, faster execution, and ease of maintenance. Our experiences demonstrate significantly reduced development time and improved scalability over the Perl approach, despite initial training requirements.

lorne
Download Presentation

HELGA - A Call Load Generator

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HELGA - A Call Load Generator Bagirath Krishnamachari Lucent Technologies, Bangalore, India Eighth International Erlang/OTP User Conference November 19, 2002

  2. Outline • The Problem Statement • A non-Erlang solution • The Erlang Solution • Experiences

  3. The Problem Statement • Need a load generator for testing a 1xEV-DO RNC • Need to run multiple calls (concurrency) • Need to simulate multiple interconnected Base Stations (distributed tool) • Handoffs between “Base Stations” (rpc, process migration) • Tool should be fast • Need to be generate reports/snapshots • Platform - Solaris/Linux

  4. Reference Architecture 1xEV-DO BTS 1xEV-DO RNC PDSN IP Network 1xEV-DO BTS

  5. A non-Erlang solution • Use Perl • Pros • Short development time • Easy to maintain and enhance • Cons • Concurrency not an inherent feature • Inter-node communication interface needs to be defined • Speed • Scalability

  6. The Erlang solution • Pros • Concurrency, distributed nodes etc are inherent • Behaviour for FSMs available • Faster execution than Perl • Shorter development time • Easier to maintain and enhance • Cons • “Different” language - training needed

  7. The Erlang solution (contd) • Modules/Features used • gen_fsm for simulating the “mobile” • Binaries, Erlang IPC • gen_tcp/gen_udp for the interface to the RNC • pg2 for managing the pool of “mobiles” • spawn/4 for inter-BTS handoffs • ets, random, ...

  8. Experiences with Erlang • Learning curve is short and steep • Development time < half of that for Perl (approx) • Speed = Five times that of Perl (approx) • Scalability - same code for standalone/distributed tool • Difficult to find “early adopters” - but we’re working on it 

More Related