LMMS / LMMS/lmms.io

Website performance/reliability issues

Open
#417 40 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

maintenance php
Dominant language
PHP
Stars
115
Forks
60
Avg merge
14h 5m
Merged PRs (30d)
1

Description

Due to an influx of high-resource requests against the website, the website keeps going down. I've temporarily disabled the forums (again) to keep the main website alive... Some thoughts/tasks on this topic...

* [x] Slow or prevent the bots constantly crawling our PHP pages, causing a lot of database requests
* [ ] Implement a more performant way to handle these requests
* [x] Investigate some storms that have occurred by non-bots (possible DDoS)
* [x] Review LSP code/database efficiency for long-running processes
* [ ] Review phpBB plugins for helping with long-running processes

HIstorically, we've allowed all websites to crawl our page as it helps people get answers they need quickly however the bots have gotten out of control... Here's a 12-hour snapshot of our nginx access logs....

Any additional help is greatly appreciated. This is a volunteer-lead website and resources are limited.

```bash
sudo cat /var/log/nginx/access.log |grep bingbot |wc -l
```

```
bot hits
-----------------
bingbot 10717
PetalBot 7206
Amazonbot 5517
Googlebot 5085
SemrushBot 4670
MJ12bot 4114
AwarioBot 3899
UptimeRobot 3550
ChatGPT 1614
AhrefsBot 952
YandexBot 497
PerplexityBot 181
DuckDuckBot 24
DiscordBot 21
trendictionbot 18
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing /var/log/nginx/access.log and running the provided bingbot count command to characterize request volume. Then investigate the two unchecked tasks: a more performant request-handling approach and phpBB plugins for long-running processes. Done means the website remains available under high-resource traffic and both areas have a documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx, php
Domain
backend, devops, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.