Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 180
    • Issues 180
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Merge Requests
  • !430

Open
Opened Jul 22, 2025 by Przemyslaw Kaminski@cgenie
  • Report abuse
Report abuse

"[Server slowness] With the dev branch on the dev instance, we're experiencing a real slowness"

Ref #495

WARNING Merge this first: !429

  • TSArchive strategy by default for timeouts (i.e. don't retry, just archive the task)
  • add more detailed phylo progress report (but for 500+ terms it is still slow when reporting progress, because of pure functions that are used there)
  • some haskell-bee fixes were made, upgraded dependency
  • POST /phylo endpoint was removed, it triggered phylo recompute. I consider that dangerous, as it can stall the server. I didn't migrate this to workers, because, from what I saw, it's not used by the frontend anyways.
Edited Jul 25, 2025 by Przemyslaw Kaminski

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch origin
git checkout -b 495-dev-phylo-fixes origin/495-dev-phylo-fixes

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/dev
git merge --no-ff 495-dev-phylo-fixes

Step 4. Push the result of the merge to GitLab

git push origin dev

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 1
  • Commits 9
  • Pipelines 4
  • Changes 18
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
1
Labels
Ready to merge
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!430