Quantcast

Assigning Issues taking a long time

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Assigning Issues taking a long time

george.ranjan

I have a SonarQube 5.0.1 installation.  It takes ages to assign an issue and drill down to the source code.  The first one is especially a pain.

 

DB and SonarQube are installed on the same machine.  Any clues where I need to start looking?  Am I undersized?  Following is my configuration.

 

Counts

About 17 projects

Each having about 22 modules, 3M Lines of Code & 200K issues

 

Memory Settings are as follows:

 

sonar.properties

sonar.web.javaOpts=-Xmx1024M -XX:MaxPermSize=160m -XX:+HeapDumpOnOutOfMemoryError

sonar.search.javaOpts=-Xmx4096M -Xms2G

 

Postgres

shared_buffers = 256MB

effective_cache_size = 2048MB

 

Regards
Ranjan

 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Assigning Issues taking a long time

george.ranjan
My guess is that it is taking time in doing some sort of indexing that is taking a lot of time as update for just an assignee cannot be taking so long.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Assigning Issues taking a long time

george.ranjan
In reply to this post by george.ranjan
Some additional information on this. I turned on server logging to "FULL" and noticed that the main time was getting consumed as shown below between inserting the record into issue_changes and the following select issue query. It seems to be waiting and polling for some notifications.

2015.05.28 14:18:02 INFO  http-bio-0.0.0.0-9000-exec-2 web[sql]  15ms Executed SQL: update issues set action_plan_key=?, severity=?, manual_severity=?, message=?, line=?, effort_to_fix=?, technical_debt=?, status=?, resolution=?, checksum=?, reporter=?, assignee=?, author_login=?, root_component_id=?, issue_attributes=?, issue_creation_date=?, issue_update_date=?, issue_close_date=?, updated_at=? where kee = ? - parameters are: ...
2015.05.28 14:18:02 INFO  http-bio-0.0.0.0-9000-exec-2 web[sql]  0ms Executed SQL: INSERT INTO issue_changes (kee, issue_key, user_login, change_type, change_data, created_at, updated_at, issue_change_creation_date) VALUES (?, ?, ?, ?, ?, ?, ?, ?) - parameters are: ...
2015.05.28 14:18:38 INFO  pool-5-thread-1 web[sql]  0ms Executed SQL: select id, data from notifications order by id asc limit ? - parameters are: <1>
2015.05.28 14:19:38 INFO  pool-5-thread-1 web[sql]  0ms Executed SQL: select id, data from notifications order by id asc limit ? - parameters are: <1>
2015.05.28 14:20:38 INFO  pool-5-thread-1 web[sql]  0ms Executed SQL: select id, data from notifications order by id asc limit ? - parameters are: <1>
2015.05.28 14:20:53 INFO  pool-2-thread-3 web[sql]  171370ms Executed SQL: select i.kee,root.uuid,i.updated_at,i.action_plan_key,i.assignee,i.effort_to_fix,i.issue_attributes,i.line,i.message,i.resolution,i.severity,i.status,i.technical_debt,i.reporter,i.author_login,i.issue_close_date,i.issue_creation_date,i.issue_update_date,r.plugin_name,r.plugin_rule_key,r.language,p.uuid,p.module_uuid,p.module_uuid_path,p.path from issues i inner join rules r on r.id=i.rule_id inner join projects p on p.id=i.component_id inner join projects root on root.id=i.root_component_id where i.updated_at>? - parameters are: ...
2015.05.28 14:20:53 INFO  pool-2-thread-3 web[bulk]  15ms ES bulk request for [Action 'UpdateRequest' for key '9b985185-349f-48a8-9762-21ec952c66ea' on index 'issues' on type 'issue'],
2015.05.28 14:20:53 INFO  pool-2-thread-3 web[refresh]  63ms ES refresh request on indices 'issues'
2015.05.28 14:20:53 INFO  http-bio-0.0.0.0-9000-exec-2 web[get]  0ms ES get request for key 'intellijinspection:ConstantConditions' on index 'rules' on type 'rule'

Loading...