Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,463,400
Community Members
 
Community Events
176
Community Groups

High CPU load after upgrading

Rene Groeschke3
Rene Groeschke Jul 23, 2015

Hey there,

since we upgrade fisheye from 3.7 to 3.8.1 in gradle open source project, We're seeing high cpu load constantly caused by the fisheye process. We havn't changed anything in configuration and just using one incremental-indexer thread. Is anybody else seeing this issue. We would really like to track this down. any help and advice is highly appreciated as our server is now running with 98% caused by fisheye. restarting doesn't solve the issue. is there anything I can look for in the debug logs that might give me a hint?

 

cheers,

René Gröschke

 

Answer
Watch
Like Be the first to like this
420 views

1 answer

0 votes
davelahn
davelahn Jul 23, 2015

Hi,

The best way to figure out what is going on would be to take some thread dumps during the high CPU load, or to use a tool such as jvmtop to get a better idea of which threads are taking up a lot of CPU.

We have some instructions here on how to generate thread dumps.

It could be for example, this open bug:
https://jira.atlassian.com/browse/CRUC-6593

However, there are many possible causes, so the best way forward would be to get a few sets of thread dumps at a 15 second interval during high CPU load. Please open up a support ticket if you'd like us to investigate further.

Best regards,

Dave Lahn 

Reply

Suggest an answer

Log in or Sign up to answer
Fisheye
Fisheye/Crucible
TAGS

Atlassian Community Events

See all events