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 186
    • Issues 186
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • 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
  • !445

Open
Opened Sep 12, 2025 by Przemyslaw Kaminski@cgenie
  • Report abuse
Report abuse

Resolve "On IMT Instance : Error message or crashes when changing the status of terms in large batch"

Ref #505

This is an experimental fix of the query that slowed down IMT in issue #505 (postgres poor config also slowed it down).

This terms query: https://imt.sub.gargantext.org/#/lists/pk@imt.sub.gargantext.org/132587 takes 11-13 seconds now. The new query, from my tests in psql, should take around 5s.

The improvement isn't 2x always like that. E.g. for https://imt.sub.gargantext.org/#/lists/pk@imt.sub.gargantext.org/132530 it's around 2.5s for old query vs 1.8s for the new one.

Still, it should be faster overall, and less complex that the older one.

Check out, review, and merge locally

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

git fetch origin
git checkout -b 505-dev-search-query-performance-fix origin/505-dev-search-query-performance-fix

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 505-dev-search-query-performance-fix

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 0
  • Commits 2
  • Pipelines 2
  • Changes 1
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
2
Labels
Doing terms table
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!445