Share Technology Points

Hi, Issue: My virtual development machine is allocated 8 GB RAM out of 16 GB of Host. Still it runs very slow. In order to develop things I have to stop the Search service and memory consumption reduced to ~5GB from 6-7GB. But this is just a work around what if I need to build some module which requires Search service. A quick investigation in Task Manager highlight Memory usage by search components are much large then other processes.  Several NodeRunner.exe processes consume lots of Memory and CPU. The culprit processes are Microsoft SharePoint Search component. Although there is no problem with just killing the noderunner.exe processes in Task Manager; SharePoint creates them again almost immediately. Cause: The architecture of search has undergone lot of changes in SharePoint 2013. Many of the core components are replaced by the FAST Search components. Below are a few new components which are added in the new architecture Crawl Component Content Processing Component Query P...

Hi Guys, I was facing a very strange issue since two three days. I just wasted lot of my time while solving it. After experiencing SharePoint 2013 service architecture, I was under the impression that MS have modified SharePoint this time that one will never face any issue while configuring the service applications. But I was wrong, I am talking about the Search service application here. If you are lucky then it may be the case that you will not see this issue but I wasn't actually explored the reason behind the issue. Issue Description: “Unable to retrieve topology component health states. This may be because the admin component is not up and running.” The default content source “Local SharePoint Sites” is inconsistent. It doesn’t always appear after creation of Search, sometimes with start addresses of existing web apps listed already, other times not. Starting a full crawl results in stuck in ‘starting’.                        Tried Solutions:  Installed all hotfixes by ...