Ticket #1040 (reopened defect)

Opened 3 years ago

Last modified 3 years ago

[testsuite][PROFILING] engine_sync_stress & engine_sync_read_write_stress doesn't complete in 30 seconds

Reported by: dgollub Owned by: dgollub
Priority: normal Milestone: OpenSync 0.41
Component: OpenSync: Testsuite Version: 0.38
Severity: critical Keywords:
Cc:

Description

engine_sync_stress

Needs to complete in 30 seconds. This is not the case. After briefly profiling it should be decided if the current design is able to perform 1000 sync-and-block calls or not. The number should be reduced to perform a stable maximum within 30 seconds.

A stable result for various testing-machine is important.

Change History

comment:1 Changed 3 years ago by dgollub

  • Status changed from new to closed
  • Resolution set to fixed

(In [5344]) Fixed #994 with r5342, r5343

Tested engine_sync_read_write_stress with 10 cycles - 10 passed. Reduced the number of stress commits in engine_sync_read_write_stress from 1000 to 250 to "workaround" #1040

Profiling to fix #1040 will be done after 0.40

fixes #994

comment:2 Changed 3 years ago by dgollub

  • Status changed from closed to reopened
  • Summary changed from [testsuite] engine_sync_stress doesn't complete in 30 seconds to [testsuite][PROFILING] engine_sync_stress doesn't complete in 30 seconds
  • Resolution fixed deleted
  • Milestone changed from OpenSync 0.39 to OpenSync 0.41

Keep this for later profiling

comment:3 Changed 3 years ago by dgollub

(In [5347]) Reduced engine_sync_stress number of iterrations from 1000 to 250. Profiling is scheduled after 0.40 release

refs #1040

comment:4 Changed 3 years ago by dgollub

  • Summary changed from [testsuite][PROFILING] engine_sync_stress doesn't complete in 30 seconds to [testsuite][PROFILING] engine_sync_stress & engine_sync_read_write_stress doesn't complete in 30 seconds
Note: See TracTickets for help on using tickets.