Search

Categories
 BigPicture

About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Progress Tracking

Tutorials and tips

Integrations

 BigPicture 7.10 and earlier

Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects


 BigPicture release notes

BigPicture Cloud Backlog

 BigGantt

About BigGantt

BigGantt installation and updates

Cloud vs. Server - Key Differences in BigPicture on These Platforms

 BigGantt release notes

Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 Trello

 BigPicture Enterprise
 Jira Cloud

 Jira Server

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Trust Center

BigPicture 8 is here!

Discover the landmark edition of the Atlassian Marketplace top-selling app! The new version is available to all Cloud, Server and Data Center users. Visit BigPicture 8 Documentation to learn more about it.

We have redesigned our algorithm responsible for replicating Work Breakdown structures across cluster nodes in JIRA Data Center. The new algorithm affects all versions released after 2018-02-15 including BigGantt, BigPicture and BigPicture Enterprise.

Please find the graphs below showing time comparison needed to copy and read data from a cluster. There has been lots of optimization implemented so only few read / write operations require data serialization across the JIRA Data Center cluster.

It is also worth mentioning that data replication in our products comprises of lots of operation and is more sophisticated than replicating tree objects only. Nevertheless, tree replication is one of the heaviest operations in terms of resources needed (CPU, bandwidth).


BigPicture / BigGantt tree component performance improvement - serialization in a cluster

The graph shows time (in seconds) needed to seralizeone-million items tree object across two node cluster. In real life examples, a typical work breakdown structure contains between 500 and 50.000 issues.


BigPicture / BigGantt tree component performance improvement - deserialization in a cluster

The graph shows time (in seconds) needed to deseralize one-million items tree object across two node cluster. In real life examples, a typical work breakdown structure contains between 500 and 50.000 issues.

BigPicture / BigGantt tree component data size

The test was performed on 10K objects tree.

Version
before 2018-02-15850kb
after 2018-02-15350kb
  • No labels