Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
22

My problem solved! Have a follow this link. Turn off distributed cache: Site loading time with it off: site loading time with it on: !!! From 6.10 seconds down to 79 ms


17

You should reduce it, and your farm will get benefit from it. Their is no impact rather you will get performance improvement. NodeRunner.exe is resource hungry process. their 3 step process: Use Set-SPEnterpriseSearchService -PerformanceLevel Reduced to reduce the CPU impact the search service Modify the C:\Program Files\Microsoft Office Servers\15.0\...


11

SPWeb.Lists.TryGetList is probably what you're looking for. So in your example: logList = site.RootWeb.Lists.TryGetList("Log Records");


11

by default the level is set to maximum when you install the sharepoint search service, Thats because on a live service you expect it to be fast with optimum hardware to support it with the correct topology to break the load from the search service! setting it to reduced is the correct way go about it: on dev machine: Set-SPEnterpriseSearchService -...


11

Generally speaking you will want to use SPQuery to only query items you're interested in. Unless you're doing SPList oList = web.GetList("XYZ"); for(int i=0; i < oList.Items.Count; i++) { string strLstItemName = oList.Items[i].Name; // << BAD, as you use Items here, so you fetch them from DB each loop } there shouldn't be any relevant ...


9

Depending on your content, that could be a very normal amount of RAM being used so I wouldnt worry about that. The very first thing to find out is what is using that much CPU, so pull up Task Manager on the server, go to Processes then check the button/box at the bottom to show all processes from all users. Click on the CPU column and look for the big ...


9

You're within the limitations of SharePoint (http://technet.microsoft.com/en-us/library/cc262787.aspx) in either scenario, which is good. Some of my thoughts As far as performance, I don't think you'll see much in way of improvement going from one DB to multiple DBs, unless you can move the DB files to different disk arrays. 100GB is a reasonable size for ...


9

Since you haven't specified what error occurs, below is demonstrated how to load multiple list items by their ids: var listTitle = 'Tasks'; //list title var ids = [1,2,3]; //item ids var ctx = SP.ClientContext.get_current(); var web = ctx.get_web(); var list = web.get_lists().getByTitle(listTitle); var result = []; //for storing items ids.forEach(...


8

There's two very simple ways: Use the Developer Dashboard feature in SharePoint 2010 - it allows you to see where the server spends time rendering your page Use the IE9 Network profiler (F12 in IE9 and the Network profiler tab)


8

The various property bags are backed by Hashtable objects, except for SPWeb.Properties which is a StringDictionary (essentially a strongly-typed, non-generic Hashtable). SPWeb.AllProperties is a Hashtable and is prefered to AllProperties (it also does not force lowercase key values). The performance of all these containers is excellent (see for example here)...


8

For driving SP 2013 with only 12 GB of RAM I recommend that you stop the search from doing continous crawls, and to stop any services that you do not plan to use. Otherwise you will ned a bit more memory. The search continous crawl uses a massive amount of system resources, so in a low performance environment, it should be turned of if it is not extremely ...


7

This is almost certainly due to the lack of caching on the content coming from the external site. How long does a request to the site normally take? Consider adding some caching, or displaying the content on your page asynchronously. And indeed, are you sure that you've not got a hidden list somewhere being used as a cache? i've seen that done. I presume ...


7

A few things in addition to the tips in Mike's link: If this is a publishing site, you might look into enabling output caching For all sites, enabling BLOB Caching can help performance Change the full and incremental crawls of your search to only run off hours. I've seen places that re-indexed all content every 10 minutes and then wondered why the site was ...


7

WHAT I PRESUME 1) you are working with custom js code 2) you are working with a custom page SOLUTION 1) don't use ScriptLink : If you register a .js file by adding a ScriptLink control to an .aspx page, the control registers all .js dependencies. To import the various "SP" namespaces, such as those listed at ECMAScript Object Model Reference, you must ...


6

If your web part gets data from an external source, do this asynchronously if at all possible, as if the external source is down, it might time out the entire page.


6

Is it possible to do a similar trace on the external web page you are getting your data from? If this page is suffering from the performance inconsistency you may have found your culprit. If not, can you replace the external page with a mocked up static page that you control? If you can control the datasource it will help you ensure that anything you are ...


6

there are several good ways of retreiving data. Each has its pros and cons. Typically Search would be used when you want to list some, but not all, data (not all can be exposed) and when you want to retrieve data across site collectons. SPQuery, SPSiteDataQuery and PortalSitemapProvider are good candidates if you are on the same site collection. See some ...


6

Leading on from @tylerrrr07's answer, there's another overload of GetItemsWithUniquePermissions which may be of use to you: MSDN: SPList.GetItemsWithUniquePermissions Method (int maxItemToReturn, bool folderOnly) You could then avoid the potentially huge result set from running the method by using the following: SPList.GetItemsWithUniquePermissions(1, ...


6

SSD will bring you outstanding improvements. Your cpu & amount of ram are already excellent so going to a flash memory drive will allow the machine to free itself. On the other side, you can optimize SQL Server (check out the recovery model, auto growth settings, etc.), Windows Server 2008 R2 (turn off everything uneeded) and SP as well (turn all ...


6

Problem solved and it was a very strange one (or maybe not). There is custom IHttpModule deployed that handles auditing view on list items. Client wanted to log everything so custom module was developed and deployed. Something like this: Sharepoint (WSS/MOSS) Auditing VIEW On List Items But if you read my question again you will see that there was problem ...


6

For me, reprovisioning the distributed cache service resolved the performance issue: $serviceInstance. = Get-SPServiceInstance | Where { $_.TypeName -like "Distributed Cache"} $serviceInstance.Unprovision() $serviceInstance.Provision()


6

I'd guess the culprit would be: SPFile file = web.Files[0]; This will load the entire collection into memory, even though you are only after a specific file. Use SPWeb.GetFile() instead. Edit Additionally, SharePoint 2007 and WSS 3.0 Dispose Patterns by Example provides an example of using the SPLimitedWebPartManager, that requires an explicit Dispose() ...


5

Are you surprised to see that it takes 7 seconds, or are you surprised to see that there seems to be some caching going on somewhere, even though you have not implemented any? I think the problem is more likely to be related to the actual datasource than your web part implementation. Does retrieval of the data involve an HTTP web request (like screen ...


5

As one of the developers behind a popular SharePoint Auditing solution, let me share my 2 cents. Auditing in SharePoint is (deeply) flawed and you are right to be concerned about performance, specifically: Audit logs grow out of control as too much information is logged by default in certain areas, (and too little in other areas). For example requests to ....


5

There are so many better ways to improve the performance and scalability of SharePoint than trying to partition site collections across web applications. If you highly optiimize your logical and physical disk IO for SQL Server, partitioning the site collections across multiple content databases on a single web application may provide less contention and ...


5

Best practice is to use SPQuery on the list to return list items that match your criteria. See the software performance boundaries documentation here has some details (pertaining to 2007): http://technet.microsoft.com/en-us/library/cc287790%28office.12%29.aspx 2010 info is here: http://technet.microsoft.com/en-us/library/cc262787.aspx There was another ...


5

Alex, Please verify and check the following sections: System Settings > Manage Services on Server Ensure that "Web Analytics Data Processing Service" and "Web Analytics Web Service" is running Monitoring > Review Job Definitions Change the service to "Microsoft SharePoint Foundation Usage" Make sure the "Microsoft SharePoint Foundation Usage Data ...


5

Have you tried Fiddler? I think it would serve your purposes really well. http://www.getfiddler.com You could also enable the SharePoint Developer Dashboard to see loadtimes etc on a page. To enable it see use: $service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $addsetting =$service.DeveloperDashboardSettings $addsetting....


5

There's no magic way to speed up a crammed memory pool filled with maxed out working sets. The only way you're going to see performance improvements is to turn off the stuff you wont' be demonstrating. If you insist of showing off everything, do multiple sessions where you only show one feature/component at a time.


5

+1 for the SSD. A single hard drive (I hope it's 7200rpm) will be the bottleneck of your system. If you launch resource monitor, I bet you will often have I/O queue. 14Gb of RAM is large enough. I've run with 8GB most of time, with no specific lag, when the I/O system is performant. Especially, I ran the dev box on a small virtual server, with some RAID 0 ...


Only top voted, non community-wiki answers of a minimum length are eligible