Skip to content

Commit 606a860

Browse files
authored
DCA-352:Jira full index time consistency (atlassian#258)
* DCA-352:Update the Jira database instance class; Update Jira reindex time * DCA-352:Reword notes text * DCA-352:Remove note frome first reindex; Add note to the Scenario 1 -> Run 2; * DCA-352:Reword reindex step according; Remove optional reindex; * DCA-352:Fix after review * Update dc-apps-performance-toolkit-user-guide-jira.md
1 parent c9fefd6 commit 606a860

File tree

1 file changed

+13
-15
lines changed

1 file changed

+13
-15
lines changed

docs/dc-apps-performance-toolkit-user-guide-jira.md

Lines changed: 13 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ The Data Center App Performance Toolkit framework is also set up for concurrency
8484

8585
| Parameter | Recommended Value |
8686
| --------- | ----------------- |
87-
| Database instance class | [db.m5.large](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html#Concepts.DBInstanceClass.Summary) |
87+
| Database instance class | [db.m5.xlarge](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html#Concepts.DBInstanceClass.Summary) |
8888
| RDS Provisioned IOPS | 1000 |
8989
| Master (admin) password | Password1! |
9090
| Enable RDS Multi-AZ deployment | true |
@@ -309,14 +309,16 @@ After [Importing the main dataset](#importingdataset), you'll now have to pre-lo
309309
Do not close or interrupt the session. It will take about two hours to upload attachments to Elastic File Storage (EFS).
310310
{{% /note %}}
311311

312-
### <a id="reindexing"></a> Re-indexing Jira Data Center (~1 hour)
312+
### <a id="reindexing"></a> Re-indexing Jira Data Center (~30 min)
313313

314314
For more information, go to [Re-indexing Jira](https://confluence.atlassian.com/adminjiraserver/search-indexing-938847710.html).
315315

316316
1. Log in as a user with the **Jira System Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html).
317317
1. Go to **![cog icon](/platform/marketplace/images/cog.png) &gt; System &gt; Indexing**.
318-
1. Select the **Lock one Jira node and rebuild index** option.
318+
1. Select the **Full re-index** option.
319319
1. Click **Re-Index** and wait until re-indexing is completed.
320+
1. **Take a screenshot of the acknowledgment screen** displaying the re-index time and Lucene index timing.
321+
1. Attach the screenshot to your DCHELP ticket.
320322

321323
Jira will be unavailable for some time during the re-indexing process. When finished, the **Acknowledge** button will be available on the re-indexing page.
322324

@@ -405,28 +407,24 @@ Review `results_summary.log` file under artifacts dir location. Make sure that o
405407

406408
#### <a id="regressionrun2"></a> Run 2 (~50 min + Lucene Index timing test)
407409

408-
If you are submitting a Jira app, you are required to conduct a Lucene Index timing test. This involves conducting a foreground re-index on a single-node Data Center deployment (without and with your app installed) and a dataset that has 1M issues.
409-
410-
First, benchmark your re-index time without your app installed:
410+
If you are submitting a Jira app, you are required to conduct a Lucene Index timing test. This involves conducting a foreground re-index on a single-node Data Center deployment (with your app installed) and a dataset that has 1M issues.
411411

412412
{{% note %}}
413-
Jira 7 index time for 1M issues on a User Guide [recommended configuration](#quick-start-parameters) is about ~100 min, Jira 8 index time is about ~40 min.
413+
Jira 7 index time for 1M issues on a User Guide [recommended configuration](#quick-start-parameters) is about ~100 min, Jira 8 index time is about ~30 min.
414414
{{% /note %}}
415415

416-
1. Go to **![cog icon](/platform/marketplace/images/cog.png) &gt; System &gt; Indexing**.
417-
1. Select the **Lock one Jira node and rebuild index** option.
418-
1. Click **Re-Index** and wait until re-indexing is completed.
419-
1. **Take a screenshot of the acknowledgment screen** displaying the re-index time and Lucene index timing.
420-
1. Attach the screenshot to your DC HELP ticket.
416+
{{% note %}}
417+
If your Amazon RDS DB instance class is lower then db.m5.xlarge it is required to wait ~2 hours after previous reindex finish before starting a new one.
418+
{{% /note %}}
421419

422-
Next, benchmark your re-index time with your app installed:
420+
Benchmark your re-index time with your app installed:
423421

424422
1. Install the app you want to test.
425423
1. Go to **![cog icon](/platform/marketplace/images/cog.png) &gt; System &gt; Indexing**.
426-
1. Select the **Lock one Jira node and rebuild index** option.
424+
1. Select the **Full re-index** option.
427425
1. Click **Re-Index** and wait until re-indexing is completed.
428426
1. **Take a screenshot of the acknowledgment screen** displaying the re-index time and Lucene index timing.
429-
1. Attach the screenshot to your DC HELP ticket.
427+
1. Attach the screenshot to your DCHELP ticket.
430428

431429
After attaching both screenshots to your DC HELP ticket, move on to performance results generation with an app installed:
432430

0 commit comments

Comments
 (0)