Net::EasyTCP uses a single process multiplexing model, which is pretty good. The downside is that it only handles one request at a time, so when it is busy running one of your functions, everyone else waits. I think you'll find this is a problem if you send in a lot of requests in parallel. The alternative is to fork, which would lose the only advantage it had over mod_perl/FastCGI.