[ARVADOS] created: a329f06e31462d59d853838beffd077ce732d631

[git at public.curoverse.com]

        at  a329f06e31462d59d853838beffd077ce732d631 (commit)


commit a329f06e31462d59d853838beffd077ce732d631
Author: Radhika Chippada <radhika at curoverse.com>
Date:   Tue Mar 24 09:49:38 2015 -0400

    5534: When a pipeline has long running jobs with hundreds of thousands of log lines, the log line display is timing out
    fetching all those lines. Limiting the number of log lines retrieved helped resolve this issue. Using limit size of 2000.
    I was able to see log when I limited to 10000 log lines as well, but it took much longer wait time and I felt a quicker
    response might provide a better user experience and hence using 2000 log lines as the limit. Thus the most recent 2000
    log lines are fetched, followed by newer log lines from event log if the job is still running.

diff --git a/apps/workbench/app/helpers/jobs_helper.rb b/apps/workbench/app/helpers/jobs_helper.rb
index 06c3d0d..2403313 100644
--- a/apps/workbench/app/helpers/jobs_helper.rb
+++ b/apps/workbench/app/helpers/jobs_helper.rb
@@ -3,7 +3,7 @@ module JobsHelper
     results = []
 
     log_history = Log.where(event_type: 'stderr',
-                            object_uuid: job_uuids).order('id DESC')
+                            object_uuid: job_uuids).limit(2000).order('id DESC')
     if !log_history.results.empty?
       reversed_results = log_history.results.reverse
       reversed_results.each do |entry|

-----------------------------------------------------------------------


hooks/post-receive
--