Hot answers tagged

7

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 ...


3

Yes, it's still valid, as it's still a SharePoint. You can read more about the limits at TechNet site: https://technet.microsoft.com/en-us/library/cc262787.aspx As you can see limitation are the same for SharePoint 2013 on premise and SharePoint online


3

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


2

As per MSFT the limit of items in a Library (including folder) is 30M, that's mean if you have the 1 folder in your document library that can contain upto 30M items. But real Catch is the List View Threshold, which is 5000 items per view( you can change it on prem). So if your library having more than 5K items then you have to filter the items in a way that ...


2

Probably you got more information than you posted, but just in case you didn't know yet - the proc_StartUndirtyList stored procedure is used to start a new link fixup operation. A back-end database server and front-end Web server work together to implement link fixup. The back-end database server tracks forward links from list items to documents. When the ...


2

For only 34 items, I wouldn't have any qualms about doing it. Workflow engine performance is affected when large numbers of workflows are paused at the same time because each time the timer job runs, it basically decompresses every paused workflow to check whether it's time to resume the workflow, and if not it then re-compresses the workflow until the next ...


2

A different way to doing this is to use retention policies. You can get them to run off a given date field as well as set it to X days/months/years. No need to pause workflows as you simply run the workflows when needed. Retention should be under settings for the library/list. (Please note that I use SP2013 but it should work in SP2010 as well: ...


2

The general view seems to be that REST is indeed more "chatty", i.e. more calls are required than CSOM and more traffic goes back and forth (although REST payloads are smaller) BUT, REST can still be faster in terms of the overall time taken. It will vary depending on different situations. My personal preference is to use REST over CSOM, especially whenever ...


2

As long as you stick to the principle of storing the SPListItemCollection in a variable before looping through the items, the difference between using for instead of foreach is close to redundant. The foreach loop will be converted into a for loop under the hood. It's a 1, perhaps 2 sec, difference. So if you write: var listItems = ...


1

Their are couple of reasons which cause the performance issue. High CPU utilization on WFE, Memory Usage on WFE High CPU and Memory Usage on the Database Traffic Unuassal Traffic on the sharepoint Structure the Farm/ site collections in a way it exceeds the MSFT recomendations i.e List views threshold violate number of columns number of web applications ...


1

Certain things can optimize it if you haven't used:- 1) Get only those columns which you require eg if you need only Title and FileReaf column then use like the below one query.ViewFields = string.Concat("", ""); 2) Set row limit It would be more easier if you can provide number of pages in that library and your caml ...


1

it is depend upon the requirement, as per my experience we increase this timing to 2 hours on one web application out of many. The Web Page Security Validation feature helps enhance security by imposing a time limit on Web pages when a user submits information to the server. When a user tries to submit information to the server after the ...


1

When you create a cache host, it should use 10% of the memory size. I say should, because that doesn’t happen all the time. Sometimes it uses 50% the memory, and sometimes 5%. Don’t ask why. But you can see the configuration of the cache cluster if you run Export-CacheClusterConfig. Use-CacheCluster Export-CacheClusterConfig -path ...


1

You should be able to do it via CAML. The query should be somewhat like this: <Where> <Or> <Eq> <FieldRef Name='ID' /> <Value Type='Number'>{FirstID}</Value> </Eq> <Eq> <FieldRef Name='ID' /> <Value Type='Number'>{SecondID}</Value> ...


1

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 ...


1

The paused workflows are serialized into the database when they are inactive, this reduces any performance concerns. When it comes time for them to "wake up" the workflow timer job brings them back to life so to speak. Based on your volume, you will be fine.


1

The Search Result web part has a set of pre-loaded display templates. So that is the reason you see templates get loaded that aren't necessary. The list of pre-loaded templates is the following: "~sitecollection/_catalogs/masterpage/Display Templates/Search/Group_Default.js", "~sitecollection/_catalogs/masterpage/Display Templates/Search/Item_Default.js", ...


1

You can use Visual Studio 2013/2015 Web performance and load tests feature: https://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC381 https://msdn.microsoft.com/en-us/library/jj710162.aspx For the question, "how many users request per second ,latency , average number of users per day" you can use IIS Logs ...


1

You can measure the time by using a global variable like this: window.StartTime = new Date() And in your onQuerySuccess() console.log("The query returned after" + ((new Date() - window.StartTime) / (60*60)) + " seconds") You could try to use REST based api for better performance... https://msdn.microsoft.com/de-de/library/office/JJ163876.aspx


1

In the context of general c# comparistions between for and foreach - There is a pretty comphrensive discussion here for loops on List are a bit more than 2 times cheaper than foreach loops on List. Looping on array is around 2 times cheaper than looping on List. As a consequence, looping on array using for is 5 times cheaper than looping on List ...


1

Background services is the way to go for servers, SharePoint has a lot of processes running in the background and none or almost none running as programs itself. What this setting does is to give the program or background service the priority to recources of the machine. clients like windows 7 and 8 run with the setting on "Program" since they need to open ...


1

In terms of troubleshooting the root cause of your performance issues, can you provide any potential finding and analysis produced from the event viewer? If you go to the Event Viewer > Application and Service Logs > Microsoft-Workflow, then right-click and select View > Show Analytics and Debug Logs. This should provide you some information regarding the ...


1

Complex tasks such as creating Web Applications, Site Collections and Sites (SPWeb) can sometimes be slow. A lot of things happen under the hood, which makes the current browser window unresponsive at times. But this is natural in SharePoint. To verify performance you should use SharePoint. Navigate between different objects, open documents, edit properties ...


1

Common actions in Office 365 takes up to one second to perform with OOTB web parts or wiki pages. There are really no performance difference between wiki pages unless you collect and filter a lot of data in web parts. If so, web part pages are slower doe to heavier data load. I think your case boils down to Internet bandwidth, internal network load issue. ...


1

If anyone is still struggling with this the answer is here. I also had very slow performance, I increased the memory allocated to the Distributed Cache from the default of 410MB to 7168MB and now my site is behaving as it should do.


1

For the record, i will add a fast resume of (mostly) all the tips to fine tune SharePoint 2013 for use in a low resource machine (i.e. developer machine or testing machine). Its not a how-to answer but it could leads to solve some problem Installing the root certificate, disable the clr check or send clr.microsoft.com to the 127.0.0.1. It speed ups the ...



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