You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dc-apps-performance-toolkit-user-guide-jira.md
+13-15Lines changed: 13 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ The Data Center App Performance Toolkit framework is also set up for concurrency
84
84
85
85
| Parameter | Recommended Value |
86
86
| --------- | ----------------- |
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)|
88
88
| RDS Provisioned IOPS | 1000 |
89
89
| Master (admin) password | Password1! |
90
90
| Enable RDS Multi-AZ deployment | true |
@@ -309,14 +309,16 @@ After [Importing the main dataset](#importingdataset), you'll now have to pre-lo
309
309
Do not close or interrupt the session. It will take about two hours to upload attachments to Elastic File Storage (EFS).
310
310
{{% /note %}}
311
311
312
-
### <a id="reindexing"></a> Re-indexing Jira Data Center (~1 hour)
312
+
### <a id="reindexing"></a> Re-indexing Jira Data Center (~30 min)
313
313
314
314
For more information, go to [Re-indexing Jira](https://confluence.atlassian.com/adminjiraserver/search-indexing-938847710.html).
315
315
316
316
1. Log in as a user with the **Jira System Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html).
317
317
1. Go to ** > System > Indexing**.
318
-
1. Select the **Lock one Jira node and rebuild index** option.
318
+
1. Select the **Full re-index** option.
319
319
1. Click **Re-Index** and waituntil 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.
320
322
321
323
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.
322
324
@@ -405,28 +407,24 @@ Review `results_summary.log` file under artifacts dir location. Make sure that o
405
407
406
408
#### <a id="regressionrun2"></a> Run 2 (~50 min + Lucene Index timing test)
407
409
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.
411
411
412
412
{{% note %}}
413
-
Jira 7 index timefor 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 timefor 1M issues on a User Guide [recommended configuration](#quick-start-parameters) is about ~100 min, Jira 8 index time is about ~30 min.
414
414
{{% /note %}}
415
415
416
-
1. Go to ** > System > Indexing**.
417
-
1. Select the **Lock one Jira node and rebuild index** option.
418
-
1. Click **Re-Index** and waituntil 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 %}}
421
419
422
-
Next, benchmark your re-index time with your app installed:
420
+
Benchmark your re-index time with your app installed:
423
421
424
422
1. Install the app you want to test.
425
423
1. Go to ** > System > Indexing**.
426
-
1. Select the **Lock one Jira node and rebuild index** option.
424
+
1. Select the **Full re-index** option.
427
425
1. Click **Re-Index** and waituntil re-indexing is completed.
428
426
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.
430
428
431
429
After attaching both screenshots to your DC HELP ticket, move on to performance results generation with an app installed:
0 commit comments