I was wondering whether there are any recommended open source performance and memory profilers equivalent to Redgate? This is for .Net and SharePoint development.
Thanks.
Chris.
Eqatech has a free performance profiler, but it only works down to the method level.
NProf statistical profiler for .NET applications.
Commercial (not free): Memprofiler and Redgate's ANTS profiler are both excellent and worth purchasing. As is JetBrain's dotTrace.
Related
I was working previously on No-Sql like MongoDB. Now I want to switch to ETL process, for that I was searching ETL tools which integrate to MongoDB, Hadoop and that tool should be having good community edition or open source because of initially I want to learn ETL so currently not possible to buy the Enterprise Edition, so any one knows which one is good ETL tool which satisfied my requirement.
One of the best is definitely Talend Open Studio for Big Data. But it requires a lot of hacking for effective work (you may need to implement your own components or inject custom Java-code to get the desired result).
I think Kettle is one of the most popular (at least from what I have noticed).
Kettle
It has a lot of features and is "fairly" user friendly.
Check out StreamSets Data Collector. It has a modern web based interface and a growing community. It's Apache 2.0 licensed. Supports much of the Hadoop ecosystem and mongodb out of the box.
Full disclosure: I'm a committer on this project.
We were using IronRuby in our applications for some simple scripting of biz logic and rules.
We are trying to upgrade everything to .NET 4.5 - and our ScriptRuntime/IronRuby code is not happy with that. It does not lok like IronRuby has had a lot of traction lately, so we are wondering what would be a good scripting engine to switch to that is best supported by a .NET 4.5 environment. We prefer simple - the less third-party stuff we have to bring in the better. OUr scripts are also simple - not a big effort to convert.
Suggestions?
If converting your scripts to C# isn't a problem, I would recommend looking into the Microsoft "Roslyn" CTP and its Scripting API.
Because the .NET compiler developers are currently rebuilding their compilers in the Roslyn architecture and the Visual Studio team intends to consume the Roslyn compilers in the future, it's a safe bet that support for this scenario will remain for quite some time.
If you're not looking to consume the Roslyn architecture, you could also leverage Windows PowerShell by writing a custom host application that can execute PowerShell scripts that contain your business logic.
We ran Jmeter on our application and found that our web server was running relatively slow. I have asked this before but I was hoping to find some free tools can I use to profile it and identify bottlnecks ?
Also do I need to look at memory profiling on the server? What are the best steps I can take towards optimizing the web server performance ? Basically I am trying to optimize the web server to the fullest so just wanted to know all the steps can be taken to do it.
So,if anyone can list all the steps or optimizations than can be done on web server when using asp.net mvc 2.0, IIS 7.0 and SQL Server 2005.Thanks for all your help.
Check out the MVC mini profiler. Written by the StackOverFlow people
http://code.google.com/p/mvc-mini-profiler/
These are great tools and have a 14 day free trial:
http://www.red-gate.com/products/dotnet-development/ants-memory-profiler/
http://www.red-gate.com/products/dotnet-development/ants-performance-profiler/
http://www.jetbrains.com/profiler/buy/index.jsp - Definitely not free, but pretty intuitive and very helpful.
What tools to use to find out what cause a high CPU usage in .net application?
WPF / C# 3.0 / .net 3.5
Apply a profiler to understand where the CPU is being used: what parts of your code are "hot". You can then review the design of those parts of the code.
Note, the high CPU usage could be completely reasonable.
First you need to find out where your application spends most of the CPU time - I suggest you run a performance profiler such as:
JetBrains DotTrace
ANTS Performance Profiler
And see where you spend most of the time.
If you want to profile specific bottlenecks you can try using Stopwatch. I've written the details at my blog.
Agreed, you need a profiler. Visual Studio 2010 Premium or Ultimate Edition has a built-in profiler. I haven't used it but it should be useful as an alternative to DotTrace or ANTS.
http://msdn.microsoft.com/en-us/library/z9z62c29.aspx
VS2013 already comes with a very good build-in profiler
I have been sold on the fun of using linq in areas other than pure database interaction. (See Calling fellow code nerds - Alternatives to Nested Loops?).
We are stuck on 2.0. I have told the powers that be about the ease of updating to 3.5 (we have already migrated to VS2008) but they are wanting a list of "benefits" for upgrading.
Can those that have experience in 3.5 help provide some talking points for the benefits of updating an existing app to 3.5?
UPDATE: Found an additional reason: Microsoft's inclusion of Charting tools for Asp.Net as a patch on top of 3.5! They get their business value, I get the fun...
Can YOU make a case for it? Sounds like you want it because LINQ is fun. Other people are mentioning features that are fun. I've always had a problem selling fun features to management because they aren't very compelling reasons to potentially disrupt an environment.
Honestly, it really depends on what you are using C# for. Are you a web developer, system admin, something else? Taking a general approach, I would use the following selling points (you will need to do some work to prove these things):
Zero-disruption for end-users when upgrading. Upgrading to the new version will be seamless and we will have a thoroughly reviewed test plan for updating all clients to this version. All of our old applications that require .NET 1.x or .NET 2.0 will still work perfectly.
Programmer Efficiency. You could mention how more of the Windows API is wrapped by .NET classes, thus making programmer more efficient because they don't have to P/Invoke as much. LINQ makes your more productive because of x, y, and z. Lambda expressions make you more productive because of x, y, and z.
Ease pains of future OS migration. Moving to WPF now will prepare us for Vista/Windows 7. We won't have to migrate applications using the now deprecated "Windows Forms" to WPF, because we will already be using it.
More applications purchased from 3rd parties will require it, so we will have to upgrade sooner or later.
In the end, you need to prove that at the very least, this move will not cost you money in terms of increased support or testing costs. If you can show it will make you be more productive and it will be a rather painless switch, then you will get your wish.
Maybe you should talk to some Java developers who are probably still forced to develop using 1.3 or 1.4 despite 1.5 being out for over 3 years and 1.6 for a couple... it appears platform consistency across the business is often of greater importance than the benefits of using the latest and greatest.
Also remember that 3.5 is just additional BCL libraries. You are still running on CLR 2.0. Same is true for 3.0. Usually when people find out that the underlying framework is the same and that you are just adding in new libraries they are more likely to go along with it.
You don't need .NET 3.5 to get LINQ or C# 3.0 features. You can implement your own LINQ for .NET 2.0. I am using C# 3.0 all over the place in my .NET 2.0 application. I don't know the full details on how to start the conversion process because I didn't set it up myself. This might be a good link for you: http://www.danielmoth.com/Blog/2007/05/using-c-30-from-net-20.html.
http://msdn.microsoft.com/en-us/library/ms171868.aspx
Transitioning onto 3.5 would help you reap the benefits/ features of:
LINQ to (Entities/ XML / Objects / Datasets etc ).
WCF, WF and WPF.
ASP.net MVC where MVC is kind of a de facto standard in other
platforms like Ruby/Python which
allow you pure HTML/ Javacript based
development.
ORM options with ADO.net Entity
Framework/ Linq to Sql
4.
With a few addons you can have
support for dynamic languages
like
IronPython/IronRuby.
Oh ya I almost forgot ADO.net Data Services..one of my fav.
These are the few benefits that immediately come to my mind.
In my experience, the addition of LINQ and Extension methods alone have made many previously arduous and/or time consuming tasks much easier and faster. The increased developer productivity from that alone is worth the upgrade effort IMHO.
Lambda expressions are awesome. There is no end to the places where I find that lambda expressions help me out in a very concise and readable way.
Automatic properties, while being a simple concept, really help making the code base smaller and clearer.
Also, I sencond the extension methods.
Before I even opened this question I had my answer: LINQ - it's one of the greatest extensions ever in .NET - I love it. It took me a few days to figure out, but now I've got it, I use it all over the place. The ability to query collections and arrays is worth the upgrade alone in my mind.
Decreased development time (and therefore increased ROI)
Less time wasted finding workarounds for .NET bugs that've been fixed in newer releases.
Extension methods for native types (in a similar fashion to JavaScript prototyping)
LINQ extensions - they take a couple of days to get your head around, but it's awesome!
LINQ to XML makes working with XML so much simpler
LINQ to objects/collections
A nice new 3.5 poster from Microsoft that you can pin up in your cubicle.
As a manager if I have a happier more productive team that is producing more in less time, then its a no brainer.
Ask yourself this: Will the developers be more effective and will their increased productivity actually increase benefit to the company or reduce corporate costs once you've considered the upgrade/transition/installation on the servers/additional testing etc? If the answer is truly yes, then do the upgrade and quit arguing about it.