FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login
    1. Home
    2. prithwhat
    3. Topics
    P
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 9
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by prithwhat

    • P

      Unsolved Certain pages taking a lot of time to load and throwing an error in background after migration from 1.36.6 to 1.54.0

      Q&A
      • • • prithwhat
      9
      0
      Votes
      9
      Posts
      11.0k
      Views

      P

      @mark-robustelli Before I move to this activity, I wanted to share an observation that I made just now

      So turns out that the error that I posted doesn't turn up every time I open up one of those pages

      It occurs when I open those pages consecutively and the CPU spikes to the "requests" range

      So to give you an example:

      Click on Users -> Takes around 20s to load -> CPU Spike observed but within request range -> No error in container logs

      Click on Users -> Immediately click on Reports/Login -> Move to Reports/Registration -> CPU spikes above request range -> Error in Container logs

      So could this be a performance tuning issue?

      As for your query about the config

      Users: 7061
      Applications: 6700
      Tenants: 8200

      Fusionauth is running on GKE on an n2d-standard-8 (8 vCPU, 32 GB RAM) nodepool, I've already mentioned the resources allocated to the deployment via the helmchart in the original thread message^

    • P

      Unsolved FusionAuth keeps restarting after upgrade from version 1.36.6 -> 1.38.1 even after successful migrations

      Q&A
      • • • prithwhat
      6
      0
      Votes
      6
      Posts
      1.1k
      Views

      P

      @mark-robustelli

      It's possible, I didn't really keep track of that per se

      We eventually moved on from this version and jumped to 1.40.x and surprisingly there were no issues in that version so this post can be closed

      That being said, I did face a similar issue in a newer version for which I might post another thread