none
Suggestion Req :) - For Project Publish RRS feed

  • Question

  • Hi,

    We have  a Few PDP Pages where we are having our own visual webparts, which is updating custom fields and publishing the projects, While  in some of the pages we are even building the team. and this whole process takes 30 SECs. But customer wants it to be more efficient and whole process should not take more than 5-10 Sec.

    Is there any way by which we can make the process more efficient. ?

    We have consider following options But these options are ruled out:

    1. Publishing the Project Offline

    2. Updating the Project Team offline.

    Please note we are using the Web Services here, not WCF


    Thanks, Parth

    Friday, December 28, 2012 1:41 PM

All replies

  • Hi Parth,

    In this case, I'll first find the exceution time for each process & that may decide the possible workarounds & making the code efficient.
    1.When you have lot of custom fields & you are looping through the records in CFdataset from Customfieldsweb services, Would prefer to use the LINQ to make query more efficient  (I am sure you might be using the lastest methods/objects of .NET3.5 ). Check the code execution.
    2. Would also check if the project that I am updating though the code, taking longer time. YOu can check with any of the out of the nox PDP to compare the code exceution & OOB update/publish & should give you a good comparison of code activity excution vs OOB update/publish time.
    3. Will not wait for the Queue or any thread.sleep to avoid the sluggish execution time & throw the publish job to queue & come out from the loop. 
    4. Also, review the infra to see how the Queue job is responding.
    5. if require add additional App server in Farm etc.
    6. Would run the same update/publish project activity on server to see if there is any network latency issue.

    Above points are just to make sure that we don't have any inefficient code etc but as per my experience, making the updates & publishing the project definitely takes more than 10 seconds. Making a  5-10 seconds response time may not be feasible.

    Hope that helps.


    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”. Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82

    Monday, December 31, 2012 8:31 AM
  • Will not wait for the Queue or any thread.sleep to avoid the sluggish execution time & throw the publish job to queue & come out from the loop

    Hi,

    If I will not wait for the queue response, how will I know that project has checked out and project update is done and then I am suppose to publish the project, I agree that after publish I should not wait for the queue to respond but before that what..!!? should I not wait for the above process to complete???


    Thanks, Parth

    Wednesday, January 2, 2013 5:46 AM
  • Hi there--

    The check-out operation is synchronous and is processed immediately so why do you need to wait for the queue? You just call the method & get the exception if any (e.g projectalreadycheckedout etc).

    As a good practice, We should use the wait for the queue so that user can understand that what's going on but if that creates impact your execution time, you may avoid that.

    Hope that helps.


    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”. Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82

    Wednesday, January 2, 2013 6:12 AM