[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-543) Is it expected for SyncBackendLongWorklistsStressTest to take ~40s

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39351#action_39351 ] 

Sanne Grinovero commented on HSEARCH-543:
-----------------------------------------

There's nothing wrong going on, it's that slow because there are 3000 commit operations involved - on purpose as the test doesn't care about the amount of entities but the length of the queue of operations sent to the backend. This is another time-sensitive test, it's setting "3000" as an insane high amount to make sure the issue will trigger, but there's in facto no guarantee and it might be lots faster if it could exit as soon as condition is verified. So right I'll rework it, together with the async version of the same test these steal more than a minute from each run.

> Is it expected for SyncBackendLongWorklistsStressTest to take ~40s
> ------------------------------------------------------------------
>
>                 Key: HSEARCH-543
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-543
>             Project: Hibernate Search
>          Issue Type: Task
>          Components: build
>         Environment: 
>            Reporter: Emmanuel Bernard
>            Assignee: Sanne Grinovero
>
> I wonder if it is expected for the test to take so long. 40 secs for 3000 entities seems long to me. DEBUG logs do not seem to be the bottlenech.
> Note that most of the time is spent before the query counting is executed. As if async was not used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira