Search results

Thanks! We had tried it on x86 solaris 10 as well. :-)

Yes, you can specify the order of contexts from the admin interface by clicking the "+"/"-" sign in the sequence colume. Regex context with lower sequence number will be tried first.

Please stay with fcgi for production use for now, a pretty bad bug have been found, which will affect post request with large request body. Fix will be in next RC release. Sorry. That will be great if you can help us iron out the kqueue bug by sending us a core file, you need to set...

That's correct, explicit matching always takes place before regex matching. It is the current design. Noop, at this point. Actually, it should be faster than using regex matching.

I think the core dump is kqueue related, not lsapi, please try poll, see if it restart so often. If you can make it dump a core file and send it to us for analysis, we will iron out the bug quickly. :-) You may need to change some kernel configuration to allow core dump for setuid process...

I think your test case is DB bounded. Even though, lsws should be slightly faster than Apache, you may want to try tuning the concurrent level of lsws fcgi. In your test, Apache made 50 concurrent queries to MySQL, but lsws fcgi only made 10, according to your configuration posted in...

It doesn't looks right, I don't think the performance of lsws and Apache is in the same class, especially for the fcgi test. Would you mind prividing more detail information about how the test is performed? What is the simple-test_script does? hardware, software used.

If you try adding a context from web admin interface, you will find it is very easy to add a CGI context. :-)

You need to creat a "CGI" context and copy the executable to the directory that the context refers to. For example, with default installation, just copy the executable "foo" under lsws/DEFAULT?cgi-bin/, then access url http://<host>/cgi-bin/foo to execute it.

click the name of the virtual host, then "context" tab, then "add"

There should be a CRLF after '[OR]', each rewrite condition should take one line. :-)

he means for the web admin interface. :-)

Yes, you need to define a external app for each fast cgi application. It is a bad idea to write too many fcgi, which only do one simple task like a CGI, you should combine features as you could. In the case of /fcgi-bin/echo, you should not define a script handler, instead, you need to...

Would you mind explaining it more clearly? :-) What log do you refer to? What is the correct value, what is not? Thanks.

Well, maybe you need to read the document throughly. Use the phpFCGI external application as an example. You can make it. :-)

Ok, we will add a favicon.ico then. :-)

LSWS needs to handle PHP memory leaks as well, it is controled by a environment variable of the PHP process. For the performance factor, just check our benchmark page, http://www.litespeedtech.com/benchmark.html All benchmark results are almost the BEST request rate you can get with...

It depends on your budget on hardware, you have to invest more on hardware (HPC or cluster) to archive the same level performance that a FastCGI application can provide on a budget server. Again, it is also depends on your application, if your DB query take long time to execute, then it will...

Are you trying to run echo as cgi or fast cgi? it can be started in both mode. You need to make sure echo works in command line first. For configure a FastCGI application, please follow: http://www.litespeedtech.com/docs/HowTo_QA.html#qa_extapp

I think C/C++ fastcgi always gives the best performance. How big a difference it will make depends on the speed of your db queries and computations. But C/C++ fastCGI is much more difficult to code. So, it depends what is your first priority. :-)