Is there a temporary downgrade option?

[theRKF]

I'm trying to determine if the current 8 core license is the best option for our server. I'd like to temporarily downgrade for a few hours/days to benchmark the differences.

From what I understand from the wiki and forums if I want to downgrade I have to change my license (only at the end of the billing cycle?), then upgrade again later and pay for the upgrade.

Is there no config option or anything that will limit Litespeed to a lower number of CPUs?

If not, can we put that down as a feature request? Clearly the functionality is there as the number of cores used changes with the license - no re-install required. We just need a way to toggle it more directly aside from swapping licenses.

[webizen]

Originally Posted by theRKF

...
Is there no config option or anything that will limit Litespeed to a lower number of CPUs?
...

You can bind all listener(s) to specific CPU(s) (Admin Console => Configuration => Listener => General => Bindings)

[theRKF]

Originally Posted by webizen

You can bind all listener(s) to specific CPU(s) (Admin Console => Configuration => Listener => General => Bindings)

Thanks - just to make sure I don't screw this up ...

I don't have that path that you described.

From Home (admin console) I click Configuration, then Listeners (0), but that's where I lose track.

There is no General option, and no Listeners defined.

I'm looking at http://exampleserver.com:12345/confi...gr.php?m=sltop

[webizen]

For control panel environment like your case, you need to create a listener in Admin Console for port 80 and bind CPUs to it. The listener created in admin cp will take precedence over the ones defined in httpd.conf.

[theRKF]

Great, thanks. Do I need to create a separate listener for 443 for SSL traffic?

[theRKF]

Another question:

Does it matter which cores I assign the listeners to? Our server has a quad core cpu with hyperthreading, so it reports 8 cores. (It seems we mistakenly purchased an 8 cpu license, even though I think we should only have a max of 4.)

I'm wondering if for this test binding to 2 cpus does it matter if I'm assigning to hyperthreading cores vs actual.

Bind to cpus 1 & 2? 1 & 3? Other? Doesn't matter?

[webizen]

Originally Posted by theRKF

Great, thanks. Do I need to create a separate listener for 443 for SSL traffic?

Yes, you need to create a separate listener for SSL traffic.

[webizen]

Originally Posted by theRKF

Another question:

Does it matter which cores I assign the listeners to? Our server has a quad core cpu with hyperthreading, so it reports 8 cores. (It seems we mistakenly purchased an 8 cpu license, even though I think we should only have a max of 4.)

I'm wondering if for this test binding to 2 cpus does it matter if I'm assigning to hyperthreading cores vs actual.

Bind to cpus 1 & 2? 1 & 3? Other? Doesn't matter?

Does not matter as long as 2 CPUs are bound.

[theRKF]

Originally Posted by webizen

Yes, you need to create a separate listener for SSL traffic.

So you have an actual step-by-step guide? The docs say what needs doing, but not the how.

[webizen]

I thought it was self explanatory.

By default, there is no native LSWS listener created when import Apache httpd.conf. In this case, you need to create a native LSWS listener in Admin Console to override Apache listener:
1. Create/Add a listener in Admin Console => Configuration => Listeners.
2. Bind to ANY or the IP server is listening to.
3. You will see error status (Admin Console => Actions) for the newly created listener after LSWS restart. Just ignore that.