Support

xing · #1 11-21-2006, 02:43 PM

LiteSpeed Web Server 3.0 public beta has been released.

3.0beta has been production tested and is deemed stable. We still recommend early adopters to test on development server before going live on production. This is pre-release software and we welcome any feedbacks and bug reports.

Download links are at the bottom of this post.

Major Changes:

Standard/Enterprise
Revamped web console: Streamlined layout, improved configuration parsing and processing to handle 1000+ virtual hosts.
Request Filtering (compatible with SecFilterSelective of mod_security)

Enterprise
IP to GeoLocation Database Support (compatible with Maxmind/mod_geoip)
64bit binaries

Standard
Sendfile() support enabled.
Max Concurrent Connections: 150

Known Issues:

Web Console is designed to be compatible with Mozilla/Firefox/IE/Opera. Older and cli browsers such as lynx will not be fully supported.
Context Sensitive Help is not active. Will be fixed in RC1.
Documentation is still formatted for version 2.X. Will be fixed in RC1.
Left menu on FireFox will display extra "Collapsed. Click to Expand." debug string. Arrow graphic missing. Fixed in RC1.

Stefan Soellner · #2 11-22-2006, 01:01 AM

Great news. Thanks for further improvements.

I will stay with 2.2.5 standard, cause I prefer a higher max cc level (300). No need for sendfile() and mod_security support.

Bye,
Stefan

Tomh · #3 11-22-2006, 05:54 AM

Will the final standard edition have 300 concurrent connections again or does this mean its permanently decreased to 150?

xing · #4 11-22-2006, 11:53 AM

Tomh, 3.0 standard will have 150 max cc and is a permanent decision. Note that based on our experience majority of our standard users will never exceed 150 max cc usage. Unless you are pushing more than a million pages/hits a day, it will never affect your performance.

Tomh · #5 11-22-2006, 03:54 PM

Ok just for the record, when you mean concurrent users you mean:

- users who are all at the same second active downloading files from your server
- when they are done they close the connection?
- they use 1 connection for all files

also what happens if user 151 connects?

xing · #6 11-22-2006, 04:24 PM

It's not Concurrent Users, rather it's max connections or in another words, max concurrent connections. 150 concurrent connections can support magnitudes more concurrent users, unless you have users that are downloading very large files that takes a long time to process.

So if 150 users are all downloading a 50MB file at the same second, that would be 150 connections and if the 151st user comes in to download and you have the standard edition, the connection request is queued meaning it will not be processed until someone out of the initial 150 download finishes.

Tomh · #7 11-22-2006, 04:54 PM

Ok, that sounds clear to me. Gonna try out this wonderfull webserver right now

TOYOU · #8 11-23-2006, 01:28 PM

Though I pity upon every inch of free pie I lose (this time it is 150 concurrent users) , I doubt that one day I will have face this issue and cry like a child.

It is an almost astounding how fast you develop your enterprise.

Soon I will test it and anticipate a big pleasure knocking this forum in a dispair trying to find a reason for my foolishness.

Fantastic.