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

PDMLink 9.0 M030 and ProE WF 4.0 M040 Performances Measurement

Highlighted

PDMLink 9.0 M030 and ProE WF 4.0 M040 Performances Measurement

Hi, we are having some relative problems of performances while doing basic actions such as login, Add to Workspace and the common refresh of workspace. The download is very much ok. We have implemented most recommendation on either the client or server side.
We would like to be able to establish a benchmarks regarding some base actions. As anyone be able to set required debug on ProE, Apache, MethodServer that allows to make clear timing measurement of the various components involved in a particular action?
3 REPLIES 3

RE: PDMLink 9.0 M030 and ProE WF 4.0 M040 Performances Measurement

There is a new Benchmark documentation and sample data that has been published in January. Anyone used it?
There are some very useful debug/logs properties to setup. Then once the tests are carried out, anyone know how to build a response map according to some tasks with all the information? I would like to know for example when we are checkout some items and refreshing the workspace what actions are done on the client, then how long it take to transfer to SOAP request to the server, how long it takes by the server to proceed the request etc...

PDMLink 9.0 M030 and ProE WF 4.0 M040 Performances Measurement

Didn't know about this. We'll also check it out.

Very interested being able to know sub-times for each part of the
process.

We've also been very interested in having a standard data set that each
customer could choose to check into their production system in a test
context if desired. Sounds that is being included.

thank you

RE: PDMLink 9.0 M030 and ProE WF 4.0 M040 Performances Measurement

it is indeed a very good starting point. It will be interesting to see what information about sub-tasks and optimization options are available from that.

I just think it is sometimes very frustrating for users to "wait" for something to happen not knowing what is exactly happening behind the scene. A Simple effort of UI to display subtask will make people understand and so being less complaining about performances as there is lots happening. But there is also some issues around the perf of communication between client and server that needs to be clarified.
Hopefully we can exchange info on all this.
cheers