-
Notifications
You must be signed in to change notification settings - Fork 671
Very slow startup of web / http manager #1076
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I see you are loading 12 repos. How large are they? |
Hello, Thank you for the quick response. The repositories are not large - but why should that count? Are you pre-loading the repos? This should be done lazy, no? I'm running on Debian - Digital Ocean droplet - SSD with 1gb of RAM. Restarted gitblit to watch RAM usage - stayed at 392 MB. Files are local. The strange thing is that now it works ok. I have no idea what changed. I did reboot the machine to fix it but it was still loading slow. Now, I logged to get information for a response and decided to restart the service just because. Now it loads fast. It might do some network checks when it starts and the network was running slow, and now it's ok?
p.s. You can use the files for systemd config examples. |
Yes. Pre-loading & caching. This is to reduce request processing time. |
Could you do that in a worker thread or lazy during startup? |
Possibly, but we have not identified this as the source of your slowdown.
|
True :). Thanks again for the support. |
Hi, Any way to shorten the loading time? |
|
* Make the CommitCache fully thread-safe. It was using a ConcurrentHashMap containing lists, but then handed out these lists. It also did multiple operations on that map that as a whole should be atomic. * Use isEmpty() instead of size() == 0. * Run the loading of the commit cache in a background daemon thread
Issue #1076: load commit cache in a background thread
I'm pretty sure something's messed up with caching. On a fresh install (with the existing several hundred repos) it's like half a minute. Then eventually it slows down. Now I clocked it, 18 minutes. Then I changed web.activityCacheDays to 3 (from the default 14), and it went down to 16 seconds. From 1113 seconds. Speaking of nonlinear... |
Hello,
I have configured gitblit on my machine and all was well until now. It seems whenever I start /restart the service it takes very long time to start SSH Manger and the web gui.
As you can see, it takes
Started @136214ms
to start =136 secondsThe text was updated successfully, but these errors were encountered: