Metastorm E-work 6.5

Bets Wait

We are currently running Metastorm E-work 6.5 (Yeah, I know it's outdated) on a Microsoft 2003 Server, Ms-Sql 2000.

5GB Ram

2 x dual Xeon 3.2Ghz processors

When openening forms, the response from the engine is extremely SLOW! What can we do to enhance it?

Regards

Find more posts tagged with

BPM

Comments

Scott_Leclerc

Have you performed any database maintenance on the Metastorm database recently? How large are the following tables:

eAttachment

eAlert

Have you checked the eWork Logs? What about the engine and web server's Event Logs? Anything there?

Carolyn Anderson

Things that slow a v6.5 version down: dependent fields, use of the GetField function in javascript (too much looping), 'VisibilityDependsOn', and lots of calculations. Build all processes with as few dependencies as possible and hte bare minimum of controls that are needed - the loops in the metastorm front-end code increase almost exponentially according to the number of controls.

Also, make sure you turn on caching of the scripts directory! Very important. this is a quick win and will improve performance instantly.

Bets Wait

Thank you for your replies.

We've cleared most of the e-tables, changed the Cache Options on IIS to :

Cache limited ASP files in memory to 5 and

Cache limited ASP files on disk to 2000.

and still, the initialization of several forms are extremely slow!

Once inside the form, functionality and response is ok.

Jerome_Pearce

There are many reasons for these kinds of issues, and the cause if often very difficult to see without looking at the system as a whole. Roles can cause many issues, as can all sorts of queries on non-indexed fields that have become much larger over time.

We specialise in finding such issues (and with legacy e-work systems), but it does involve a lot of hands-on investigation rather than general advice.