Re^2: A simple web server with HTTP::Daemon and threads

It's hard to expect that HTTP server rewritten in Perl will have better performance than apache. Are you sure that the problem is in apache and not in your scripts? If your script often returns the same data, you can improve performance by placing reverse proxy in front of apache, nginx is widely used for this purpose.

Comment on Re^2: A simple web server with HTTP::Daemon and threads

Replies are listed 'Best First'.
Re^3: A simple web server with HTTP::Daemon and threads by nikos (Scribe) on Feb 15, 2010 at 19:56 UTC
I was experimenting with threads in Perl. And Apache/mod_perl seemed to be an overkill for such a simple request/response script - that's why I tried to implement it purely in Perl. Of course, the main problem is DB requests. Though, apache/mod_perl takes a tremendous amount of memory. Anyway, I kept on using apache/mod_perl and got rid of DB requests at all. I stopped using mysql to keep my data and switched to memcachedb (not memcache but memcachedb). Still have this problem with memory leaks when using threads in perl. Lucky me, I don't experiment with it anymore. Thank you!	[reply]

Replies are listed 'Best First'.

Re^3: A simple web server with HTTP::Daemon and threads
by nikos (Scribe) on Feb 15, 2010 at 19:56 UTC

I was experimenting with threads in Perl. And Apache/mod_perl seemed to be an overkill for such a simple request/response script - that's why I tried to implement it purely in Perl. Of course, the main problem is DB requests. Though, apache/mod_perl takes a tremendous amount of memory. Anyway, I kept on using apache/mod_perl and got rid of DB requests at all. I stopped using mysql to keep my data and switched to memcachedb (not memcache but memcachedb). Still have this problem with memory leaks when using threads in perl. Lucky me, I don't experiment with it anymore. Thank you!

[reply]