Project

General

Profile

Actions

Task #121

closed

Stress test for workflow

Added by Vít Švanda over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Vít Švanda
Category:
Workflow
Target version:
Start date:
08/25/2016
Due date:
% Done:

100%

Estimated time:
Owner:

Description

We need know, how much workflow instances can be push to workflow engine and what impact will this have on loading time.

Actions #1

Updated by Vít Švanda over 8 years ago

  • % Done changed from 0 to 30
I use modified integration test for change user's permissions and create 12000 process instances in 45 minutes.
  • Load first page (10 items) of historic processes now takes 210 seconds.
  • After first investigation, we have two problems:
    • OR clause used for security
    • Including process variables.
Actions #2

Updated by Vít Švanda over 8 years ago

I did optmilaizations:

  • Now are applicant and implementer users included to process "involvedUsers" after process started. For subprocess I use StartSubprocessEventListener for same purpose.
  • Process variables are included only for get method. Name of process (this name is generated inner process and save only in process variable) are for list query search with specific variable query (loaded is only one variable ... not all).

Resutl:

  • Before optimalization: Load first 10 items of historic processes takes 900 seconds (for 50 000 processes)
  • After otpimalization: Load first 10 items of historic processes takes 0,5 second (for 50 000 processes)
Actions #3

Updated by Vít Švanda over 8 years ago

  • Status changed from New to Resolved
  • % Done changed from 30 to 100
Actions #4

Updated by Radek Tomiška over 8 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF