nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Open Deploy Performance

skd1

Currently I am experiencing problem with opendeploy performance.The process takes a lot of time.Please suggest the parameters that could be set to enhance the performance.

I am attaching the logs from the base and the receiver.
I am performing opendeploy and datadeploy in 38 seconds.
Of which datadeploy takes 1 second while opendeploy
for 1.5MB data takes almost 30 seconds.

Edited by skd1 on 01/26/04 04:58 PM (server time).

Find more posts tagged with

Comments

iwovGraduate

What is the data rate you get between your OD source and OD receiver ? How much time does it take to ftp/scp 1.5 MB between these two servers ?
I see that you use transactional deployment. If you make it non-transactional, you will see some improvement.

Adam Stoller

Comparing FTP / SCP to OD is not usually a straight-forward comparison.

As mentioned, transactional deployments will take longer than non-transactional deployments. Non-filelist deployments will take longer than filelist deployments.

In order to compare them, you'd need to use a non-transactional filelist deployment with reporting DISabled on *both* the sender and receiver.

You may still experience a bit of apparent lag in OpenDeploy as OD contains the overhead of setting up the connection and taking down the connection and I believe the time for doing this is incorporated in the overall elapsed time reported by OD.
In contrast, I believe SCP and FTP (for sure) tend to distinguish setup/take-down time and file transfer rate.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

skd1

I tried using non-transactional too.
I am using file list deployment.

These are few findings using normal ftp(Teamsite to Web Server) and opendeploy

When files to be deployed do not exist on destination server:
1.Using ftp: 9 sec
2.Using opendeploy: 14-16sec (with and without transaction)

When files to be deployed exist on destination server:
1.Using ftp: 13 sec
2.Using opendeploy: 30sec (with and without transaction)

The reason it is taking more time when files to be deployed exist on destination server is because of the following
process as seen in logs

id=0 server: Receiving item[./html/documents/bizproblems.doc] [reason file_list]
(3) id=0 server: dir for tempfile [/web/bizpoint/test70/bizpointDomain/applications/bizpointApp/bizpoint/cmastaticfiles/intranet/common/html/documents]
(3) id=0 server: -- Processing file(/web/bizpoint/test70/bizpointDomain/applications/bizpointApp/bizpoint/cmastaticfiles/intranet/common/html/documents/bizproblems.doc)
(3) id=0 server: file created[/web/bizpoint/test70/bizpointDomain/applications/bizpointApp/bizpoint/cmastaticfiles/intranet/common/html/documents/bizproblems.doc.iwtmp]
(3) id=0 server: Renamed [/web/bizpoint/test70/bizpointDomain/applications/bizpointApp/bizpoint/cmastaticfiles/intranet/common/html/documents/bizproblems.doc.iwtmp] to [/web/bizpoint/test70/bizpointDomain/applications/bizpointApp/bizpoint/cmastaticfiles/intranet/common/html/documents/bizproblems.doc.iwnew]

Is there a better way to handle this situation.

pflory

A thought - is OD compression enabled?

Paul Flory

Adam Stoller

Again - comparing FTP and OD is akin to comparing apples and oranges.
With FTP - did you calculate how long it took to create the FTP connection (including typing your name and password to login), and navigate to the directory where you were going to transfer the file?
Does FTP provide individual file roll-back capability (it might? I have no idea - but OD does - and that's part of what you're seeing in the logs).

Did you disable reporting on both the Base Server and Receiver (and restart the servers as needed) before doing the time tests for OpenDeploy?

OpenDeploy provides lots of functionality and as such tends to do a bit more than FTP - so if you have OD do things like set the owner of the deployed files or explicitly set the mode bits differently than they were set at the source side - you need to calculate the amount of time it will take you to do that using FTP too.

See what I mean? You need to really break it down to all the variables involved before you can do a real honest comparison. And there are likely times when a very simplistic deployment requirement might be faster with FTP - but the more complex your requirements get, chances are the better OD will perform.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

skip11

We have seen deployments take an inordinately long time when the server has a cancel pending on a job. A typical deployment lasting a few seconds could take serveral minutes. In our case, the deployment would never have worked due to routing issues, and it looks like OD was up to it's ears in overhead trying to cancel the job.

Ralph Barger
CS GROUP TOP
Zurich