Performance improvements. Performance monitoring with the help of JMX.
New in this release:
Easily find data about indexing for troubleshooting in Bitbucket UI.
Performance monitoring with the help of JMX.
Introduced the throttling approach to indexing data.
Improved indexing. Now commit data is indexed in batches to decrease the memory usage.
Awesome Graphs entries about indexing are now recorded in the awesome-graphs.log file located in the Bitbucket home directory.
Easily find data about indexing for troubleshooting in Bitbucket UI
Information about data indexed by Awesome Graphs is now available in Bitbucket Administration> Troubleshooting and support tools> System Information and in a support zip. This information is helpful when troubleshooting an app related issue and includes the following statistics:
total number of indexed contributors
total number of indexed commits
number of repositories in indexing queue
Performance monitoring with the help of JMX
Now JMX (Java Management eXtensions) can be used to expose Awesome Graphs data from Bitbucket to monitor how indexing goes. Details about the statistics that you can capture are below.
Statistics about Awesome Graphs indexing queue (com.stiltsoft.bitbucket.graphs:name=Tickets)
Name
Description
Total
Total number of tickets in the indexing queue
RepositoryTicketCount
Number of tickets for indexing of a whole repository in the indexing queue
RefChangeTicketCount
Number of tickets for indexing of changes happened after 'git push'
Introduced the throttling approach to indexing data
Indexing repositories is a resource intensive process. With adaptive throttling, Bitbucket examines the total physical memory on the machine and determines a maximum ticket number that the machine can safely support. Using this approach improves the system performance when Awesome Graphs' indexing is performed.