In the morning or after a few hours it take up to 20-30 seconds until the server sends the requested content, doesn't matter which space or page. After this first time access the content delivary is fast and really fine (below 1 second).
Found these unsolved thread on this, but unfortunately no answer to my question:
We use Confluence 6.10.1 on a virtualized Windows Server box here with a MS SQL Database (sorry, company policy). 4 Cores with 8 GB RAM and sufficient disk subsystem is in place - should be enough for approx. 50 users and only 5 editors.
Followed design guides / hardware requirements, checkt the caching statistics... no hints. BUT, currently i'm the unly user on the system!
It seems the system is sending some processes or services to sleep when it isn't used for a while. How to find them?
Thanks for any idea or hint!
Let's start digging in! You've provided a fair amount of detail, I have some ideas that hopefully we'll be able to track down with some additional info:
As a band-aid to this behavior, you might be able to check the host every so often to keep it awake. If your server is exposed to the internet, you could try setting up a check with something like UptimeRobot every 5-10 minutes or so. Behind a firewall, you could use an internal tool like PRTG or Nagios to do a keyword-based uptime check.
hopefully these are the two options we are looking for:
The confluence VM is running on a Microsoft Windows HyperV Host. I configured the VM not to use "dynamic RAM", it's permanently assigned. In the power options of the VM i already switched from "balanced" to "highest performance".
The VM itself is "awake" all the time and the service is allways available on the configured https port 443. I'm able to login via rdp or console without any delay. It's the service "Atlassian Confluence Confluence230718113355" that seems sending some subprocesses to sleep if not accessed for a while. Doing so it raises the CPU utilization for the amount of time (20-30 seconds) it takes to send the requested page and going down again after finish.
Here's some thoughts:
Just for conclusion:
confluence seems to be having a problem with Microsoft Hyper-V dynamic disks which means that disks can automatically grow as more space is needed. Converting the disk to the type 'fixed', after idle time confluence responds three times faster than before.
3x faster meaning the first-load after idle takes 7 seconds instead of 20? In that case, that's what I'm seeing right now on my Linux box. Subsequent loads are speedy, but after some period of inactivity, it takes ~7 seconds of spinning before I get a response.
It's odd because this wasn't an issue with Confluence 5...
Hey there, folks! For most of us, the past six months- yes, you read that right- have been a journey. More people than ever before have pivoted to working remotely, and navigating being on-scre...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events