RE: Project issues list load time

Tech-Archive recommends: Fix windows errors by optimizing your registry

Are you speaking about delting just the offending sites and then using
stsadmin to restore just those sites or removing all sites and restoring them?

We add one to two projects weekly to the server so the issue is not in the
creation of new sites but in the sites for certain projects. I found that
the ones affect seem to have a fairly large number of Issues in the list.
However there are some other projects with large Issues list that aren't
affected. In your experience what is the general cause of this. I would say
that if there is some record limit that is impacting performace it should
occur with all large Issues lists not just certain ones.
--
Jay, MCP


""Dana Brash"" wrote:

> Hi Jay,
>
> I understand from your other post that you have been unsuccessful in
> finding the microsoft.public.project and microsoft.public.project.server
> newsgroups. As the Issues list is specific to Project Server, this would
> generally want to get posted in the Project NGs, but I'm happy to work with
> you on the problem here.
>
> From your description, it sounds like you've eliminated PWA and network
> issues from the equation, and you've isolated it to just the issues list
> running locally on the WSS server, accessed through the Project Workspace
> URL directly.
>
> It seems also that this is not a universal behavior, but is isolated to
> specific project workspaces' issues lists. Have you tested publishing a
> new project, letting the workspace get automatically created or manually
> creating a workspace for it (depending on your settings) then adding an
> Issue to the new workspace's Issues list? Do you experience the same delay
> in behavior here?
>
> As this problem is limited to specific sites, the fastest resolution is to
> backup the sites and restore them using stsadm.exe. This will overwrite
> all the information in the site and should improve the performance. Please
> refer to the WSS Administrator's guide for instructions on using stsadm
> backup and restore.
>
> Windows SharePoint Services Administrator's Guide
> http://www.microsoft.com/downloads/details.aspx?FamilyID=a637eff6-8224-4b19-
> a6a4-3e33fa13d230&DisplayLang=en
>
> Please let me know if restoring the sites doesn't resolve the issue.
>
> Best regards,
> Dana
>
> Dana Brash [MSFT]
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --------------------
> Thread-Topic: Project issues list load time
> thread-index: AcXe9MvqWxuCFllVQkmxqquLuOIQzg==
> X-WBNR-Posting-Host: 204.4.13.72
> From: =?Utf-8?B?SmF5?= <fjm@xxxxxxxxxxxxxx>
> Subject: Project issues list load time
> Date: Tue, 1 Nov 2005 06:59:02 -0800
> Lines: 19
> Message-ID: <C50653DC-3097-4026-9AE1-DF42271CF7AA@xxxxxxxxxxxxx>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.sharepoint.teamservices
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sharepoint.teamservices:3518
> X-Tomcat-NG: microsoft.public.sharepoint.teamservices
>
> This is the Third time I've posted this.
> On certain projects the Issues page takes 60-80 seconds to load the issue
> then another 60-80 secs after you click the edit button before you can edit
> the issue.
>
>
> It doesn't matter whether you display the "Issues Page" inside PWA or
> whether you go directly to the WSS link the response is the same. In fact
> i've RD'd into the physical server and viewed them right from the browser
> in
> the console with the same results... so it's not a network related issue.
>
> BTW all servers (Project Server, SQL and WSS) reside on the same physical
> server.
>
> I posted this on the non-managed groups over a month ago with no results.
>
>
> --
> Jay, MCP
>
.

Quantcast