Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

What causes slow JIRA performance at remote server

Hi.

Gotta question:

we have Jira application at one server

as well as we i have two remote machines ( servers) - server A and server B.

Server A is common server used by many yemployees  and JIRA works normally there.

Server B is my server where I have specific software which I use to communicate with JIRA via JIRA API. I got the firewall channel between JIRA application and my Server B.

Problem: if I run JIRA in Mozilla at Server B – it is slow! For example to load welcome page takes abouts 35 secs. As well separate jira issue loading takes 36 sec as well.

What should I check? I am new for such issues….

From my server I have no channel to other applications, which I could run in Mozilla and compare the performance.

Thank you very much!

2 answers

HI, 

Nic.

Thank you for your answer!

i suspect wrong server configuraion the moust as well.

Thank you.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 25, 2020

Server B is on the other end of a slow network connection, is running under-resourced, or is overloaded by poor configuration (possibly all three).

Check the networking first, then server resources (how much memory does Jira have to run, is it on a decent CPU, is the server loaded with other tasks, is the home directory on a fast local disk on a non-shared file system?)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events