Search results

The failed requests in LiteSpeed test is due the difference in response body size, the request should be successful. I have been seeing that for long time during our internal tests. The performance difference between LiteSpeed result and nginx result is mainly because LiteSpeed start lsphp...

If you change your server, you need to migrate the license key to the new server by follow our migration procedure in the documentation. No charge for that.

According to our test, the performance difference between 32bit and 64bit of lshttpd is minimum. I am not sure about PHP.

released. :)

LiteSpeed Web Server 3.3.1 has been released. Download LSWS: http://www.litespeedtech.com/product...rver/download/ Changelog for LiteSpeed Web Server 3.3.1: Fixed a bug in static file GZIP cache. PHP build script has been improved. Fine tuning of various parameters.It is highly recommended...

Addressed. :)

Please Make a copy of info.php to info.php5, see if it works properly. Then try the "AddType" in .htaccess.

Since Rails framework initialization may take a while, one timeout added in LSWS might be too short, we have increased it in 3.3.1, please wait for the 3.3.1 release and see how it goes.

What you observed is normal log messages with 3.3 release. You need to increase the "Max Request Body Size". Also make sure the related configurations in php.ini are set properly.

You can try closing the DB connection after the framework initialization. That's because ruby LSAPI will fork all children processes off the parent, file handles to SQLite db are inherited, may cause trouble when multiple processes try to access the DB using the same file handle. Another way...

We will try, but we cannot guarantee that it will work 100% all the time due to the technical difficult.

You can download our 3.3.1 release package, the final package will be available soon. For now, just change the version number in the download link.

You do not have to use PHP suEXEC with our LSAPI version of PHP, using suexec will not affect the performance with LSAPI PHP. If you host only one large website, whether to use suEXEC is really up to you. LSWS should work well with plesk no matter what.

ignore_user_abort may only work with Apache as Apache embed PHP engine in httpd process. LSWS has no clue whether "ignore_user_about" has been set or not, and the PHP process might be assigned to another request or shutdown. We will take a closer look, it may not be possible to make it work...

Added script handler configuration for php5, it should work well now.

Maybe ruby run out of memory when parsing a file like that.

That's fine.

Does it happen with Mongrel as well? I think it should. It still puzzled me why the segmentation fault can bring down the whole VPS, as you told you that even SSH will not respond anymore. It should have something to do with the VPS software. As I knew there are a few bugs in Ruby related to...

OK, the bug has been identified, the fix will be in 3.3.1 release due in this week.

Can you PM me the login to the web admin console? I can take a look.