Migration from Oracle 9.2 to Documentum 6.0: very poor times

cquesa

Entreprise purposes are migrate from Oracle to EMC Documentum.

But times are very poor, so migration is stopped until optimization.

Actual storage system: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production

And Documentum Server Version: 6.0.0.215 Linux.Oracle

These are times measured in tests over production environment.

Save 10 files of 463k

Oracle 1,416"

Documentum 12,744"

Save 10 files of 1M

Oracle 2,514"

Documentum 15,521"

Save 10 files of 2M

Oracle 3,166"

Documentum 21,007"

Is this a performance issue of version 6.0 fixed in version 6.7?

Migration from 6.0 to 6.7 version is also in enterprise roadmap.

This is a critical enterprise issue. Appreciate any help.

Find more posts tagged with

Comments

bacham2

How do you store the documents in Oracle? Is it a single record in one table with a BLOB? If so, the comparison is not fair. Documentum has a rich content model and will create multiple objects (document, content, optionally ACL, audit trail, etc) translating in multiple inserts in multiple tables for each document, and will also save the file in its storage areas. For this you get

Also, how do you import the documents into Oracle respectively Documentum. Where do you run your code? On the Oracle box resp. Content Server or from a different machine? Which APIs do you use?

As you can see, the numbers you provide don't mean anything without context. But it's obvious that Documentum will slower. You cannot compare apples and oranges. Nevertheless, you can do better than 50 seconds for importing 10 documents into Documentum.

cquesa

The point is that poor time of 50 seconds for importing 10 documents.

May be affecting content server indexing?

Documentum architecture is based in Web service implemented with DFC API. There is also a connection pool, so Documentum connections are reused.

Alvaro_de_Andres

You are probably expending 40+ seconds when connecting to documentum through your services, once it is connected the upload time is similar to the Oracle ones. Log the connection time/upload and you'll probably confirm this. There's a lot of factors than can hit the time it takes to stablish the session with documentum.

PanfilovAB

If your compare Documentum with single table in database the answer is: yes, Documentum is much slower than Oracle (and your oracle results is not ideal - you can use direct path inserts and get milliseconds instead of seconds), but show me a real life scenario where business user should load documents so fast.

cquesa

There is a connection pool, so connections are reused in tests.

These are the times in seconds.

Save 10 files of 463k

Oracle 1,416

Documentum 12,744

Save 10 files of 1M

Oracle 2,514

Documentum 15,521

Save 10 files of 2M

Oracle 3,166

Documentum 21,007

PanfilovAB


cquesa wrote:

These are the times in seconds.

Save 10 files of 1M
Oracle        2,514
Documentum  15,521

1. if you publish some performance results you should also publish corresponding methodology (I have tried to create 10 dm_document objects with 1Mb content, it takes 3 seconds in my small dev environment)

2. there is no reason for documentum (platform) to be as fast as oracle table (data structure)

Alvaro_de_Andres

How are you uploading the content to the Oracle database? Are you in the same host? same network configuration/bandwidth/etc in both tests? Documentum is slower than a direct insert in database (because it does more than one insert ) but shouldn't be much different

I've just tested a document upload through DFS via VPN to a slow network with 3 hops (client machine -> DFS server host -> Content Server host) and has uploaded 30Mb in about 20 seconds

Julien.Fontaine

May be you should enable full trace log on your environment. Also please post your methodology and your piece of code that you use for your benchmark.

Thanks

cquesa

Network with 3 hops (web service client -> Content Server host -> Documentum Oracle 9.2 DB)

Web service in Axis 1.4 uses DFC to save metadata and document content, sets acl, i.e. common tasks in Documentum.

This web service layer maintains a Dcumentum connection pool, so in tests only a connection is used.

Documentum Server Version: 6.0.0.215 Linux.Oracle

Upgrade to content Server 6.7 may improve performance?