Bug #17674
open
add profiling infrastructure to Rails API server
0%
Description
time arv collection list --limit 1000
real 0m7.582s
user 0m0.331s
sys 0m0.057s
{"method":"GET","path":"/arvados/v1/collections","format":"html","controller":"Arvados::V1::CollectionsController","action":"index","status":200,"duration":6355.86,"vie
w":0.58,"db":1531.68,"request_id":"req-rpixy3w93ed1kr1my2p5","client_ipaddr":"127.0.0.1","client_auth":"ce8i5-gj3su-b8imt9ab31yacmz","params":{"cluster_id":"","count":"
none","forwarded_for":"ce8i5-","include":"","limit":"1000","offset":"0"},"@timestamp":"2021-05-13T18:45:26.857971730Z","@version":"1","message":"[200] GET /arvados/v1/c
ollections (Arvados::V1::CollectionsController#index)"}
The time spent fetching from the database is dominated by the time spent doing... everything else:
"db":1531.68
"duration":6355.86
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-06-09 sprint to 2021-06-23 sprint
Updated by Peter Amstutz over 3 years ago
- Subject changed from Investigate why listing records is slow to add profiling infrastructure to Rails API server
Updated by Peter Amstutz over 3 years ago
- Target version deleted (
2021-06-23 sprint)
Updated by