Posts made by mcole_1967

Hello,

We are seeing performance issues when loading the dashboard page in ProGet. Specifically loading the "DashboardFeeds" view in the database is taking anywhere from 15 to 30+ seconds to run. Sometimes the application will timeout waiting for this to happen.

We have ProGet configured with domain authentication and are only giving permissions (including read) to specific users / groups. To minimize what information unauthenticated users see we have the advanced option "Web.HideHomePageFromAnonymousUser" enabled. Despite this, hitting the root of the application without credentials seems to build the dashboard in the background before redirecting to /log-in. If multiple people (authenticated or not) try and load the dashboard at the same time then the likelihood of the application timing out requests increases.

Is there any way to prevent the application from doing the expensive dashboard build operation until after the credentials have been checked?

Would upgrading to the latest version likely help the performance at all? (Noticing a closed issue around SQL locking in the release notes..) .. or do we need likely need to throw more resources at the database server to make the page render in a reasonable amount of time?

Thanks,

Martin

Product: ProGet
Version: 5.1.8

We currently have 2 instances of ProGet talking to the same SQL server instance. The first uses the db name "proget" the second uses "proget2018".

On the second server this value is specified via the "Initial Catalog" argument in the connection string. The connection string is presented correctly with "Initial Catalog = proget2018" when prompted before upgrade from the InedoHub. After upgrade the connection string gets reset with "Initial Catalog = proget" resulting in the data being shown from the first server. It looks like schema upgrades are being applied to "proget" rather than "proget2018" during the upgrade.

Is there any way to fix this?

Product: ProGet
Version: 5.1.6