Bug #5556
closed
[Workbench] Timeout error on collection#show for a collection with large manifest text
Added by Radhika Chippada almost 10 years ago.
Updated almost 10 years ago.
Assigned To:
Radhika Chippada
Files
Related issues
1 (1 open — 0 closed)
- Category set to Workbench
Workbench with profiling enabled shows the logs#index API call taking longer than anything else, too.
I'm guessing the logs#index response contains multiple changesets, each with a "properties" hash containing a many-megabyte "old attributes" hash and a many-megabyte "new attributes" hash. Perhaps this (from CollectionsController#show) should use select() to avoid needlessly preparing/transferring/parsing those giant properties hashes:
@logs = Log.limit(RELATION_LIMIT).order("created_at DESC")
.where(object_uuid: @object.uuid).results
(Not sure, but it looks like Workbench doesn't do anything with the properties hash...)
- Status changed from New to In Progress
- Assigned To set to Radhika Chippada
- Target version changed from Bug Triage to 2015-04-01 sprint
Reviewing 655469d
The new test confirms that toggling the new configuration setting doesn't break the API client. However, it does not confirm that the setting has any effect on the API client. If the API client ignored the setting completely, I believe both tests would still pass. Tom recently added test/unit/arvados_api_test.rb which has some basic mock support to test ArvadosApiClient directly. Would it maybe be possible to use this infrastructure to confirm that request headers do or don't include Accept-Encoding, as appropriate?
Thanks.
Brett wrote:
The new test confirms that toggling the new configuration setting doesn't break the API client. However, it does not confirm that the setting has any effect on the API client. If the API client ignored the setting completely, I believe both tests would still pass. Tom recently added test/unit/arvados_api_test.rb which has some basic mock support to test ArvadosApiClient directly. Would it maybe be possible to use this infrastructure to confirm that request headers do or don't include Accept-Encoding, as appropriate?
I spent some time to see if I can see the request headers sent to server. I am not able to see this header. I did check by looking at the api server test log that the header is included. Since I did not find any easier (or other) way to see the header, I am going to move on. As you said, my goal was to verify that the code update did not have any negative side effects, which it serves. Thanks.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:46b124cc766e4e35e40c1c3e2c1b388816aa682a.
Also available in: Atom
PDF
Updated by Radhika Chippada 
Updated by 
Updated by 