You are the administrator of a Linux system that provides file and print service

Question

You are the administrator of a Linux system that provides file and print services to over 100 clients in your company. The system uses several fast SSD hard disks and has a Xeon E5 processor with 16GB of RAM. Since its installation, you have installed database software that is used by only a few users. Unfortunately, you have rarely monitored and documented performance information of this system in the past. Recently, users complain that the performance of the server is very poor. What commands could you use to narrow down the problem? Are there any other troubleshooting methods that might be useful when solving this problem?

Explanation / Answer

Disk Speed:

Poor Disk I/O will cause poor execution with inquiries, contraptions, and issues with 10+ attachments.Test the circle speed with the utility and directions from our Testing Disk Access Speed KB and contrast your outcomes and the great/awful/normal reaches.

Against infection "on get to" does not coexist with JIRA applications and the ordering index must be rejected from on-get to scanning.In a few cases, (for example, certain variants of Symantec) these prohibitions are overlooked and the issues will continue.In this case it might be important to expel hostile to infection from the server and look for another arrangement.

For Linux installations consider mounting your filesystems with noatime.This teaches the OS not to set a timestamp each time a record is read.When applications get to Lucene files and store documents a large number of times each second the atime composes can mean a recognizable stoppage as much as 30% as indicated by one case study.Before you change your mount alternatives you should make sure no other application is dependant on atime.A more preservationist setting that would at present yield benefits is "relatime".

Database:

1.Verify the heap on the database and the DB server our Testing database get to speed KB can be utilized for this.Additionally, this ought to be raised with the DBA for the server, as Atlassian Support are not specialists on diagnosing and investigating database issues.

2.Verify the validationQuery has been set according to Surviving Connection Closures and the database association is arranged according to the Connecting JIRA applications to a Database documentation.

Related Questions

Navigate

• Browse (All)
• Browse Y
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.