So Welcome on one of the many technical blogs out there on the web. So what is special about this blog? Well absolutely nothing :) ... This is the place where I store handy information I don't want to forget, while hoping that in the process I'm also helping some other poor soul on the web that is facing similar issues, or is interested in similar topics.
So who am I?
My name is Mark Priem, I was build in 1981 and live in the Netherlands together with my two sons, Roan and Levi, and my Wife Mylene (note the capital W... You know who's boss now), who I all love to death.
Aside from spending as much time as possible with my family I enjoy sports and socializing face to face and online. Your average Joe right? The little time that is left I spend on technology; My main focus currently is SharePoint and cloud solutions, which I work with on a daily basis as part of my Job, Consultant at Microsoft. As I'm a Microsoft Certified Master in SharePoint 2010 I think I can say I know a thing or two about SharePoint, which I hope has a positive effect on the quality of my posts.
If however you find any misinformation or plain wrong content, please let me know. We all make mistakes right? :)
Please enjoy your stay and let me know what you think by commenting to my posts.
Thanks!
Mark
If you're serious about SharePoint, you know Netmon. Well, if you like Netmon, then meet his big brother Message Analyzer
It's like Netmon on steroids J…
There is a lot to tell about this tool, but I won't. Hey I'm a SharePoint geek, I have better things to do!
What I can tell you is that cool things have been added like payload rendering, statistics views, and proxy capturing (ala Fiddler) which makes our lives a lot easier.Just take a look at the juice screenshot where I'm peeking in the HTTPs stream of the Connect site. Lovely!!
So get the beta from Connect and do some testing yourself!!!
Due to the many response I get: This post was written specifically for the Preview of SharePoint 2013The memory leak is resolved in RTM. Please do not apply the memory settings in production!
Just today there was some discussion on our internal DLs about the noderunner.exe processes of the Enterprise Search service being very hungry for CPU and RAM.
It turns out that there is a memory leak and a lot of debug code involved [REMEMBER: We are still at beta here J].
Jose Vigenor from MS beta support pointed to two options to contain these processes:
Good luck!