So, we are in the middle of this JQL query for getting all issues over all projects, and the response is taking hell of 7 seconds, even though overall issues are only about 300. Also, to note that the results are paginated so, each time a new request I have to make to get new issues, so those 7 seconds does include 3 calls in that sense. But can you please let me know like why it is taking too long of a time. Also, I am running my server in India, and calling to Jira cloud api somewhere out there, does that too count? Please help me out of this!
So this is basically what are we doing:
Can anybody help me get less response time, Thanks in advance!
@SahilAnower,
Can we see the JQL query itself? Or a representative example?
The query is empty in reference to this page
@ibuchanan
Thanks for replying!
Hey can you please update me on this?
@SahilAnower,
I really don’t know. I have 318 issues in my dev instance. For me a similar request returns in in <0.4s. If I wrap it all with pagination logic, that might be 1.6s not including additional programming language compute time. My best guess would be the time you are seeing is network latency.
If you want to compare results, here’s how I timed my results:
#!/usr/bin/env sh
curl \
--user $ATLASSIAN_ACCOUNT_USER:$ATLASSIAN_ACCOUNT_API_KEY \
-w @- \
-o /dev/null \
-s \
"https://devpartisan.atlassian.net/rest/api/3/search?jql=&startAt=0&maxResults=100&fields=priority,status,timespent,resolutiondate,created,duedate,assignee,project" \
<<'EOF'
time_namelookup: %{time_namelookup}\n
time_connect: %{time_connect}\n
time_appconnect: %{time_appconnect}\n
time_pretransfer: %{time_pretransfer}\n
time_redirect: %{time_redirect}\n
time_starttransfer: %{time_starttransfer}\n
----------\n
time_total: %{time_total}\n
EOF
And my results:
time_namelookup: 0.033442
time_connect: 0.078877
time_appconnect: 0.133922
time_pretransfer: 0.134290
time_redirect: 0.000000
time_starttransfer: 0.392374
----------
time_total: 0.393310
