View Full Version : How to use lsperld? Why there no instructions?
My CGI script is using too much CPU, I need some way to fix it. Specifically 1 perl script is using the majority of CPU resources. Please someone post step by step instructions on how to set this up. And if I contract with LSWS for 1 hour, would that be enough time to set it up?
01-29-2012, 08:33 PM
please refer litespeed demo admin console, access info is here:
how to set Fast CGI App for lsperld
in Virtual Hosts -> demo -> External App -> lsperld
There are no Perl/CGI apps in external apps in that admin gui panel?
And the demo is not working:
01-30-2012, 06:54 PM
please re-visit my last post
I restarted lsws in the demo admin console, and
http://demo.litespeedtech.com/perl/ is ok now :)
Demo is not working again, I had to login to admin to restart it. Why is it not working so much? Is there configuration issue or is lsperld unstable?
Can you tell me about how much money it would cost to hire litespeed to install/configure lsperld for my server?
01-31-2012, 05:07 PM
please refer our service list:
maybe "Hourly Support" for your case.
this demo YaBB forum hosted by perl has nearly 20k posts, I'm trying to clean it up. It has been running there for 6+ years.
I know about the prices. $150 an hour for configuration. I am asking how many hours would it take to setup lsperld for my server? Since litespeed and lsperld is your own creation, it shouldn't take that long right? Another question, does lsperld work with all perl scripts? I am asking this because my script is not compatible with mod_perl but it does run fine under regular perl I think. I didn't need to tweak anything to get it to work with litespeed.
01-31-2012, 09:08 PM
yes, setup lsperld won't take time, and believe you can do it well.
and I have same question with you: not sure if your script will be compatible with lsperld or how long will it take to get them working together. Suggest you set up it yourself, no more tricks than what demo shows. you can post the error messages here in error log for trouble shooting.