DocumentManagement Service Performance

I have written an application that retreives a list of folders using ListNodes within a given area and loops through them to see if the folder already exists, from a passed in parameter. If the folder does not exist it creates it and updates the nickname, it also creates 5 sub-folders within that folder using CreateFolder.

I have tested this on a folder with 655 items and it is taking over 2 minutes to run. I have tried changing the tansfermode and several other configuration changes but to no avail. Is there anything I can do to enhance performance of the service.

Find more posts tagged with

Comments

Jason_Smith

You could try using ListNodesByPage and page through the results instead of trying to get them all at once with ListNodes.

Jason

Paul_Blighe

Hi Jason

Thanks for the tip, I will give this a go but even doing a simple call to ListNodes on a folder that has 650 items is taking over 2 minutes to return. On folders with far fewer items it is returning pretty fast.

I would have thought that what I am trying to do is not that uncommom and 650 items is not that large (maybe I am wrong), within our organisation we have some folders that have upwards of 1000 items. It may be a configuration setting that I have got wrong so I have copied my binding configuration in case anyone spots something fundamental:

Appu_Nair

First I do not do a lot of webSvcs but since this is kind of a lapi replacement this could be tried and seen if this is possibly a reason.Invoke the code with a user who has 'SA' privs on the system.My guess is it ought to be faster because perm checks are bypassed.Then if it worsens for a regualr user who has perms to do things in the folder you atleast know that also.

Also it looks like you ared doing ListNodes so why do you want to create a loop to see if the folder exists.Lapi lisItems had a command that would do this(or maybe it is n oscript I forget)

select * from dtree where subtype=0 and name like 'name of folder that I am going to create'

Perhaps websvcs has a convenient one as well or you could write it yourself.

If you don't get a result then your folder can be created or else you will get the handle of the folder

Don't you thinks so

just a thought If I am wrong forgive the intrusion.

Paul_Blighe

Thanks for the comments. I have tried this with the Admin user and it is still taking over two minutes just to retreive the nodes using ListNodes. This is before looping through the result set. Retreival of folders with significantly less sub-folders is taking on average 2 seconds.

The application was originally written in lapi but we are moving towards using web services instead. If this is normal performance then we will obviously have to review their usage. However, I have not ruled out something within my client setup. It would be interesting to know if anyone else has come across this issue.

Hiren_Ganatra

Hi, I know this reply is extremely late and that the original issue probably has been resolved but I just wanted to share my take on this issue:

1). The DocManService has methods called GetNodeByPath, GetNodeByName which could help you check for the presence of a given sub-folder within a folder much faster.

2). Regarding having ~ 1000 subfolders in any given folder: I've inherited a couple of existing bespoke systems integrated with LiveLink and the previous development team had made comments about performance degradation if a folder has > 100 (hundred) subfolders. As a result when we're building any new application integrating with LL and if possible we try and stick to this rule.

-Hiren