litespeedtech / litespeedtech/openlitespeed

Is openlitespeed crippled?

Open
#470 0 comments 3 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
1.5k
Forks
233
Avg merge
2d 19h
Merged PRs (30d)
5

Description

Hi @openlitespeed I have a very honest question based on testing openlitespeed for a month now with sleepless hours.

Running openlitespeed on production, I notice that openlitespeed does not seem to use memory usage even when I set caching for files etc via the server settings. For example even if I dedicate 1gb to caching small files, I see no tangible usage of memory and performance being in some cases worse than without these caching settings which I was kind of confused about.

Further to this, I notice that changing settings like instances, I do not see the process multiplication effect I assume would happen - for example I read that online that if you increase the instances from 1 to 10 and set leaping children to say 5, you should get like 50 php processes to run? I have a production site with way more users than that and I don't see that happening.

I admit I likely dont know as much as you guys who coded it, but I think something is wrong. Openlitespeed never pushes over 300% cpu on an 8 thread cpu no matter what I try. And the side effect is slow pages and the works that comes with that. How do I get openlitespeed to consume more resources - never thought I would have to ask such an ironic question.

Please help me! Thank you!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported production behavior with file caching, instance settings, and PHP process limits, comparing resource usage and page performance. The issue provides no source files or tests to target; done would require identifying whether the behavior is incorrect and documenting or fixing the cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, php
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.