cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Nintex workflow space issue

We have a SharePoint Site collection with a single root site having a few list and minimum data. About 10 lists and 10 15 records in each list. We have a single Nintex workflow for approvals. The approval has few stages and it uses if conditions, flexi tasks and send email notification for most of its controls. there are about 50 to 60 controls used in the workflow in total.The export size of the workflow is about 2 MB. We have cleared up the logs and tasks. we have also deleted the previous versions of the workflow. The issue we are facing is that this single workflow is occupying 210MB  (analysis from /layouts/storman.aspx) of memory space out of the limited memory space that we have.

 

Kindly suggest ways to reduce the memory usage of Nintex workflow in SharePoint site.

Labels: (2)
Reply
6 Replies
Workflow Hero

Re: Nintex workflow space issue

That is quite incredible that a 2MB exported workflow contains 210 MB of diskspace. I've found several times that Storage Metrics is close, but not always exact. To find a better calculation:

  • Look at the Site Collection Quota page in CA
  • The Site Collection Web Analytics report for the site collection
  • Or PowerShell $site.Usage.Storage / 1mb

When you publish a workflow it associates a XOML file (WWF3) to the list. It's just an XML file and text, so it shouldn't be 210MB.

But, to limit the size of a workflow I would first break up the 2MB workflow. Try to create workflows at 1MB or smaller when exported. The smaller the easier to cache. For 2013 the documented XAML size to publish is 5MB, so you should be just fine.

  • Instead have a workflow call another workflow to do sub processing. If you have a branch that repeats several actions but cannot be part of a loop, call another workflow to reduce the overall size of both workflows by limiting the number of actions across them all.
  • Of course loop when appropriate instead of copying actions to occur many times.
  • Remove log to history list actions. These should only be used in debugging or limited in use during production actions. Several actions contain a log feature in the Common tab to duplicate this need.
  • Remove disabled actions
  • Use the correct condition operation, a state machine or switch over several If else's.
  • Delete unused variables
0 Kudos
Accept as Solution Reply
Not applicable

Re: Nintex workflow space issue

Hi Prakash,

Did you consider the performance recommendation provided by Nintex. If not please find the link to the document. Consider splitting the workflow into logical child workflows. Its recommended that workflow size should be around 500KB.

Thanks,

Nidish

0 Kudos
Accept as Solution Reply
Not applicable

Re: Nintex workflow space issue

Hey Nidish Kotian‌ and Prakash RS‌, you can find this document on the site here Workflow performance, timeouts and load reduction‌.

0 Kudos
Accept as Solution Reply
Not applicable

Re: Nintex workflow space issue

Hello everyone,

 

I have used several optimization techniques but were still facing the issue.

 

Finally we found out that the version history was the root cause of the issue. Nintex has hidden library "NintexWorkflows" were it stores xoml, rules and config file in addition to the default SharePoint workflow location. It creates new version each time we publish the workflow in both these locations. Removing old versions or disabling versioning did not help as the setting were restored after we republished the workflow. We had to export a copy (.nwf) of the workflow. Then remove the workflow from the workflow setting (ensure no instance is in progress) and create a new workflow from the export file.

 

Now the entire site collection storage with other lists and data  is just 10 MB.

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Nintex workflow space issue

Thank you so much for providing that insight!

If you don't mind me asking, I'm curious to how many versions where there for the single workflow? Just wondering how 1 for 1 it is per version.

0 Kudos
Accept as Solution Reply
Not applicable

Re: Nintex workflow space issue

There were about 40 versions for the workflow (since we are in the development stage)

0 Kudos
Accept as Solution Reply