Title: Message Title
Mauro Talevi updated an issue
JBehave / JBEHAVE-1073
Story duration time in multi-threading execution mode is higher than normal
Change By:
Mauro Talevi
Fix Version/s:
3.9.6
Assignee:
Mauro Talevi
From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] Sent: Wednesday, April 01, 2015 4:03 PMTo: u...@jbehave.codehaus.orgSubject: Re: [jbehave-user] Story duration are not calculated correctly in multi-thread executionSure, easy enough to do! Can you please raise a JIRA issue for this usecase?CheersOn 1 Apr 2015, at 23:56, tran, phong wrote:Hi Mauro, Yes weâre When running in multi-threading mode with 10 threads for concurrent story execution. EmbedderControls[batch=false , skip=false,generateViewAfterStories=true,ignoreFailureInStories=true,ignoreFailureInView=false,verboseFailures=true,verboseFiltering=false,storyTimeoutInSecs=108000,failOnStoryTimeout=false,threads=10] Weâre trying to speed up the test execution (Selenium-based tests) with multiple threads (threads=10) targeting a Selenium Grid with 10 nodes. I noticed that the reported duration for each story is also high and that is why the sum of all story durations added up to a high total number. Does this mean the duration at the story level has been affected with multi-threading execution mode? Do we need to de-normalize (divided by 10 in this case) the duration for each story to get its accurate execution time? It would be great if the de-normalization for story duration can be at addressed at the JBehave framework level to handle the multi-threading execution mode. Thanks,Phong From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] Sent: Saturday, March 28, 2015 1:56 AMTo: u...@jbehave.codehaus.orgSubject: Re: [jbehave-user] Story duration are not calculated correctly in multi-thread execution Hi Phong,I would imagine you're running in multi-threading mode. The total is calculated as simply be the sum of each duration. If you have a single thread then it will coincide with the build duration (more or less), but you use multiple threads it'll be off by a factor which should correspond to the number of threads. Arguably we could use the information of the threads to renormalise the total by the number of threads. This formula would still work in the case of a single thread. Can you confirm that you're using multiple threads? CheersOn 25/03/2015 08:22, tran, phong wrote:Hi Mauro, Thanks a lot for updating the core example template! We can access and integrate the durations from storyDurations.props into our custom HTML report now. However, we just notice another issue. The total duration reported in storyDurations.props for all stories is much higher (8 times) that what we usually see in our test run. Basically we have a configuration in TeamCi
