lenra-io / lenra-io/server

[Bug]: Performance problem on the server/devtool.

Open
#574 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted
Dominant language
Elixir
Stars
6
Forks
0
PR merge metrics
No merged PRs in 30d

Description

What happened?

It seems that when running a lot of requests to the server api on a lenra application, in my case a couple thousand requests, the server starts rebuilding the UI at each request and it also seems that either it reloads the UI MUCH more than at each request but more like 100 times per request or either the logging system is duplicating the logs.

In fact, my log file is 1.5 million lines long for the mere couple thousand requests, it seems quite high for that.

To reproduce this weird behavior, you can run the https://github.com/jonas-martinez/achiever app and enter your steamid + the appid that you can find in the technical.md file.

I can't upload the log file as it is literally 1 Gigabyte. I'm uploading the first thousand lines.

What browsers are you seeing the problem on?

No response

Version

No response

Relevant log output

log.txt

No response

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

Reproduce the behavior with the linked achiever app, using the Steam ID and app ID described in its technical.md file, and inspect the attached log.txt. Start at the server API request path and observe UI rebuild and logging frequency under a couple thousand requests. Done means requests no longer cause excessive UI rebuilds or produce unexpectedly duplicated log lines.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
api, backend, observability, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.