A Oracle Workspaces Web Services Performance Tips

The following are some factors that affect the performance of Oracle Workspaces Web Services:

• All the bulk operation calls take relatively more time because they have to create or retrieve bulk data. The time required for such an operation will be proportional to the number of operations being attempted in a single bulk operation call.

• Cross-workspace search is slower if the number of workspaces of which a user is a member is extremely large. In general, search operations take more time if the wild card search criterion (* or %) is given.

• The operation to list all workspaces or list the user's favorite workspaces will take more time if there are any attributes being requested through the attrRequest parameter.

• Trying to retrieve a large number of items through a list or get call will take more time.

• Creation or deletion of a workspace inherently takes more time than other operations.

• Creation or deletion of a resource in a workspace may take more time.

• Oracle Workspaces Web services operations may result in a request timeout or client socket timeout exception if the data being created or retrieved is huge. In case of operations where the data is being retrieved, the user will have to narrow down or refine his or her calls to retrieve a subset of the data he or she originally intended to retrieve. In case of create, update, or delete operations throwing a timeout exception, these operations would still go through unless there is an error in user input. The user will not get any notifications either way.