Speeding up Database Access with mod_perl
Now that we have our test program, how can we actually test it? I wrote a short Perl program using Benchmark.pm, in Listing 3. The timethese function is imported by Benchmark.pm, which we bring in at the beginning of the program. We also bring in LWP::Simple, part of the “Library for WWW access in Perl” that makes it a snap to write a small web client. How simple? Well, the following one-liner returns the HTML contents at http://www.linuxjournal.com/:
perl -e 'use LWP::Simple; print get "http://www.linuxjournal.com";'
Perl does not format the output for you. That's the difference between a web browser and a web client; the former is meant to retrieve information for humans, while the latter is meant to retrieve information for programs. In this particular case, we just want to simulate 100 retrievals of each of our programs via the web. Any timing differences will thus be due to the program on the server side—which, since they are identical, means that the differences will be due to mod_perl and Apache::DBI.
How much faster is the Apache::DBI version than its CGI counterpart? Here are the results I got running time-db.pl:
 ~% ./time-db.pl Benchmark: timing 100 iterations ... Apache::DBI: 24 secs (1.77 usr 0.67 sys = 2.44 cpu) Plain CGI: 394 secs (1.10 usr 0.61 sys = 1.71 cpu)
That's quite a difference. When I first ran this benchmark, I was convinced that the plain CGI program had somehow gotten stuck. Alas, that was not the case; the overhead associated with CGI was simply too great.
Here is a second run of the same benchmark, just for comparison.
 ~% ./time-db.pl Benchmark: timing 100 iterations ... Apache::DBI: 28 secs (1.89 usr 0.61 sys = 2.50 cpu) Plain CGI: 355 secs (1.15 usr 0.62 sys = 1.77 cpu)
Yes, it looks like CGI is indeed much slower. By the way, you can see that Apache::DBI used more CPU time than plain CGI—which means that the time was spent forking the new Perl process, rather than performing our program's computations.
What if we take out the Apache::DBI directive in srm.conf and restart the server? That would give us an indication of how much overhead was being used opening the database connection. As you can see, things do indeed slow down—although admittedly not by a huge amount:
 ~% ./time-db.pl Benchmark: timing 100 iterations ... Apache::DBI: 34 secs (1.97 usr 0.63 sys = 2.60 cpu) Plain CGI: 460 secs (1.19 usr 0.60 sys = 1.79 cpu)
The moral, then, seems to be that moving from CGI to mod_perl gives a huge performance boost, and that moving from DBI to Apache::DBI gives a moderate performance boost. The more database accesses your web applications do, the more useful these technologies will probably be in your work. Perl has always been known as a useful language, but rarely as one that can help you write fast software. Now, with mod_perl and Apache::DBI, you can write web applications quickly, and watch them run quickly as well.
Webinar: 8 Signs You’re Beyond Cron
11am CDT, April 29th
Join Linux Journal and Pat Cameron, Director of Automation Technology at HelpSystems, as they discuss the eight primary advantages of moving beyond cron job scheduling. In this webinar, you’ll learn about integrating cron with an enterprise scheduler.Join us!
- DevOps: Better Than the Sum of Its Parts
- Return of the Mac
- Drupageddon: SQL Injection, Database Abstraction and Hundreds of Thousands of Web Sites
- Play for Me, Jarvis
- Non-Linux FOSS: .NET?
- Not So Dynamic Updates
- Designing Foils with XFLR5
- Users, Permissions and Multitenant Sites
- diff -u: What's New in Kernel Development