New answers tagged

0

Here are few more things which you can do to improve performance: 1) Avoid giving reference of plugin files in each web part(ex bootstrap.css, jquery.min.js etc.), instead give references of such files in the master page itself and with the help of javascript append those references in the iframe of web parts. 2) Open audit option in console, find unused ...


0

noticed people are answering based off the web parts being the issue but 5 web parts on a page is not a lot at all. few things to note. is it a live (365) or on-premise server..... is it a live or dev server? the second part related to the hardware. What is your specs like ram, topology etc. once the above is answered the next part is the web parts(If ...


3

You can also use the SharePoint Developer dashboard to troubleshoot problems with page components. If your Developer Dashboard doesn’t offer you enough information, you can make use of SPMonitoredScope in your code. How to enable it ? To enable dashboard you need to create the Usage and Health Data Collection Service Application. Use the below powershell ...


3

I just kept more than 5 WebParts on my page but the loading time difference between page without WebPart and page with WebPart is of max 2-3 seconds. For more detailing i would like to say that i kept OOTB WebParts. And your question will not have any specific answer as the scope of answer is too wide. Still i am listing some of the thing which you must ...


2

You don't need any specific tool for that. Just remove the webparts one by one until you see the performance rise. If it never does, the performance problems are likely somewhere else


0

Microsoft need to make this clearer. There are two scenarios for doc libs: Archive (rarely used) - Place up to 30,000,000 items in a document library, but remember to create ListViews not exceeding 4,999. Filter by ID range possibly. Possibly use indexes and metadata to improve speed Migrated File Share (used a lot by multiple users) - Break up into say ...


0

SharePoint is not a relational database system. Therefore it does not have any interesting feature for query optimization. The CAML language is definitely more limited than SQL. Join type queries are difficult to make. And they are costly to performance. All SharePoint lists are stored in the same SQL table (almost). And it is not supported by ...


2

Some things to consider: Make use of the object cache. You can always beef up SQL--add more memory. You can also add more servers to your farm to open up two lanes of possible web traffic. Retention policies can be set into place to clean up an environment of unused sites, content, historical data, tests, junk, redundancy, etc. On that note, you could set ...



Top 50 recent answers are included