The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

page.max.diff.lines & page.max.changes

Seth Carter
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 21, 2025

https://support.atlassian.com/bitbucket-data-center/kb/comparison-of-a-pull-request-diff-between-bitbucket-server-and-data-center-versions-up-to-6x-and-from-7x-onwards/

Given the more efficient diff method explained above, is it now ok to bump up the max.diff.lines and max.changes limits? (running Bitbucket 8.19.9 with default limits)

Previous guidance was "Please note that increasing the limit is not recommended and will have a performance impact." explained further at link below:

Pull request is too large to render | Atlassian Support | Atlassian Documentation

 

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Aman Shrivastava
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 24, 2025

Hi @Seth Carter 

While the 2 way diff method is indeed more efficient, increasing the limits still carries a potential performance risk. If you wish to make adjustments, you can consider increasing the page.max.changes to a slightly higher value rather than a significantly larger one. We recommend monitoring the system's performance closely after implementing this change. If any performance issues arise, you can revert to the default setting of page.max.changes=1000 to ensure stability.

Regards,
Aman

TAGS
AUG Leaders

Atlassian Community Events