As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
We want a high performance testing tool for a distributed scenario
We want to collect data from clients and from server (memory usage, cpu usage, response time, .net calls etc).
Most of our applications are using .Net 4.0 or Classic Asp.
We have 4 servers. We want 1 controller and three agents working together for testing, collecting data.
What's the best tool for this scenario?
ps: We've tried Visual studio 2012 ultimate and it seems promising. I don't know other tools that fits the scenario.
Give Load Tester a try: http://www.webperformance.com/load-testing/ (disclaimer: I work there). It has a monitoring agent that will run on your Windows servers to collect the metrics you mentioned and a lot more. It also collects client-side metrics such as page load time. The LITE version is free and can run simple tests with unlimited users.
Take a look at Rational Performance Tester. I was about to purchase a license for one of our projects but didn't push through for reasons not related to the software. Looked promising back then.
I would split things up to keep it simple.
First I would check what the average requests per seconds is when using your servers to generate load. For that there is a small tool included in Apache Http Server called ab.exe. It's easy to setup to generate requests.
If you think that you get acceptable response times all is well.
If not, use something like Jetbrains DotTrace (in your app) to collect data when generating load from one server.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Whats the point of node.js creating its own server and tries listening on it, isn't IIS/apache give us all of that? I understand its based on I/O Completion but we have web-servers technology in place. Can someone explain what can be achieved via node (apart from the java script on server side, which can be also achieved via SignalR) that can't be done via ASP.NEt and why we should focus so much on node when we have a tone of technology under asp.net stack
Any classic example of node? typically for a enterprise dev. shop
Most web programming are for data display & eCommerce applications which are mostly database intensive, though lately it has been mash-up as well with web services, yes mobile web is a different game due to hardware sensors I agree but what is Node giving us which ASP.NET with SignalR can't give us?
TIA
What I find very interesting with Node is that everything is event based, which is different than programming ASP.NET or PHP where behavior is more sequential. Not a bad thing, just a different way of doing things.
You can program the server itself (as opposed to programming applications that run on the server) to do more than serving files, the typical example with Node is the chat room application where you broadcast messages to all participants and each can send messages to the server. By programming your own server events (like listen, error, connect etc) you have a lot of control over how things go server side.
Then of course npm, the node package manager, is definitely a plus over having to manually work the dependencies if you want to use 3rd party libs.
To host an ASP.NET site/app you need IIS which is a proprietary system, whereas Apache and Node are more open. Granted though, Node hosting is not as widespread as Apache based hosting.
Hope this answers some of your questions
Each technology can achieve anything. If you prefer ASP.NET over Node, use it. ASP.NET is extremely powerful and there is no reason to use Node over ASP.NET when you have the expertise and software/money to run your services. Node is just different; it has a different execution model (no threading whatsoever) and above all, it is open source and free. It is easy to get started on any OS, and easy to deploy on any OS. But in the end, it comes down to; what do you prefer?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I know you're think "hands down SQL Server" (as am I) but I'm finding myself in delicate situation that requires I "sell" this to my new supervisor (not a developer).
What I'm looking for are compelling arguments for non technical people and some that are "slightly" technical but don't really understand the differences. I'm having a hard time convincing my current shop that this is not only extremely inefficient but dangerous in so many ways. I won't be able to give them a dissertation however to convince them. What arguments can I give them "quickly" that will make them understand how serious this could be?
Thanks!
It depends really. I'd suggest sql express if money is the problem though.
Also there is this:
http://support.microsoft.com/kb/303528
Microsoft Jet is not intended for use with high-stress server
applications, high-concurrency server applications, or 24 hours a day,
seven days a week server applications. This includes server
applications, such as Web applications, commerce applications,
transactional applications, and messaging server applications. For
these types of applications, the best solution is to switch to a true
client/server-based database system, such as Microsoft Data Engine
(MSDE) or Microsoft SQL Server. When you use Microsoft Jet in
high-stress applications such as Microsoft Internet Information Server
(IIS), you may experience any one of the following problems: Database
corruption Stability issues, such as IIS crashing or locking up Sudden
failure or persistent failure of the driver to connect to a valid
database that requires re-starting the IIS service
You don't provide any info to really answer this. what is your application all about? what load will it need to handle? how much data will it retain? what are the backup and availability requirements? etc...
if you are building a little web page for internal use only, Access may get you there. for anything else, or for future expansion, for better tool integration, SQL Server is the right tool. Just download the free express version and build you application. the available features and compatibility with the purchased version are worth it alone. When you outgrow access you'll have to throw away everything and start again, with sql server express you can migrate without changing anything.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm in the process of switching from certain open-source technologies to ASP.net for building web applications (including some complex CRM and ERP tools as well as simple blog-like apps.) So far I've used MSSQL in the learning process but the more time I spend looking into infrastructure costs, the less impressed I am with MSSQL. (Windows Server / IIS on the other hand is relatively inexpensive and not a concern.) I've used MySQL in the past and feel comfortable with it.
Please provide me examples of situations, if any, where given the choice, MSSQL would justify its costs compared to MySQL. I realize there are reasons to use MSSQL such as the quality of integration out-of-the-box with Visual Studio, etc -- however I'm more interested in this from the stand-point of the raw costs of running servers. For example, if you can tell me something like "the license cost of MSSQL with one physical server will be lower than the hardware costs of running multiple servers with MySQL while providing the same performance in situation X, Y, and Z," I'd love to hear it. Perhaps there are reasons why it's cheaper to scale MSSQL or perhaps it is just a lot more efficient. People make the decision to choose MSSQL every day and I'd like to hear the reasons that pertain to cost.
I also welcome any answers that prove the costs to be negligible.
if your MySQL will scale much more than the limitations of Express, than perhaps you shouldn't use MySQL at all.
SQL Server is licensed Per CAL or Per CPU Socket(most expensive). There are also cheaper versions with fewer features but still fully functional, namely Web edition and Workgroup edition.
If money is your sole concern here, I encourage you to check the edition compare and see the one that best satisfy your needs then check the licensing info
Why not just use Sql Express? There are few limits (1gb ram, 4gb db) but besides that you can get the management tools for it, etc.
Voila - no cost : )
http://en.wikipedia.org/wiki/SQL_Server_Express
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What is the best load testing tool for ASP.NET applications?
Probably WCAT as it is MS and will give you shed load of Windows based metrics. WCAT
However Jmeter (Java FOSS) is top notch Apache Jmeter
And Selenium while not strictly a stress testing tool has many other testing features. SeleniumHQ
As i say WCAT if you are MS based is probably the best but worth casting your eye over Jmeter. Selenium is a FireFox plugin and does other testing that might interest you.
I'm fond of Siege for any HTTP load testing, or of course there's the classic ab.
Visual Studio Test Edition 2010 or any of the other SKU's that give you access to those tools.
The prices have just come out in Ed Glas's blog here.
This tool also appears in Visual Studio 2008.
The loadtesting tools that come with Visual Studio come with a great set of objects for manipulating tests. The test recording is great and Fiddler2 will record test as well.
It integrates well with your favorite ASP.Net dev environment... Okay, lame joke.
The results can be stored in a database with little effort and all perfmon stats are available for selection if required.
This is the tool for ASP.Net apps and I would use it for a Java site if I had to.
It is scalable in that Visual Studio itself can generate load for 250 virtual users (enough to bring your dev machine to it's knees). You can buy the licence for extra users to really get your "distributed denial of service" on.
There is one tool here that you can give a try.
Here is a good article that I've read recently.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am currently looking at a distributed cache solution.
If money was not an issue, which would you recommend?
www.scaleoutsoftware.com
ncache
memcacheddotnet
MS Velocity
Out of your selection I've only ever attempted to use memcached, and even then it wasn't the C#/.NET libraries.
However memcached technology is fairly well proven, just look at the sites that use it:
...The system is used by several very large, well-known sites including YouTube, LiveJournal, Slashdot, Wikipedia, SourceForge, ShowClix, GameFAQs, Facebook, Digg, Twitter, Fotolog, BoardGameGeek, NYTimes.com, deviantART, Jamendo, Kayak, VxV, ThePirateBay and Netlog.
I don't really see a reason to look at the other solution's.
Good Luck,
Brian G.
One thing that people typically forget when evaluating solutions is dedicated support.
If you go with memcached then you'll get none, because you're using completely open source software that is not backed by any vendor. Yes, the core platform is well tested by virtue of age, but the C# client libraries are probably much less so. And yes, you'll probably get some help on forums and the like, but there is no guarantee responses will be fast, and no guarantee you'll get any responses at all.
I don't know what the support for NCache or the ScaleOut cache is like, but it's something that's worth finding out before choosing them. I've dealt with many companies for support over the last few years and the support is often outsourced to people who don't even work at the company (with no chance of getting to the people who do) and this means no chance of getting quality of timely support. On the other hand I've also dealt with companies who'll escalate serious issues to the right people, fix important issues very fast, and ship you a personal patch.
One of those companies is Microsoft, which is one of the reasons that we use their software as our platform. If you have a production issue, then you can rely on their support. So my inclination would be to go with Velocity largely on this basis.
Possible the most important thing though, whichever cache you choose, is to abstract it behind your own interface (e.g. ICache) which will allow you to evaluate a number of them without holding up the rest of the development process. This means that even if your initial decision turns out not to work for you, you can switch it without breaking much of the application.
(Note: I'm assuming here that all caches have sufficient features to support what you need from them, and that all caches have sufficient and broadly similar performance. This may not be a valid assumption, in which case you'll need to provide more detail in your question as to why it isn't).
You could also add Oracle Coherence to your list. It has both .NET and Java APIs.
From microsoft : App fabric
Commerical : NCache
Open source : RIAK
We tried a couple in the end we use the SQL session provider for asp.net/mvc yes there is the overhead of the connection to the DB but our DB server is very fast and the web farm has loads of capacity so not an issue.
Very interested in RIAK has .net client and used by Yahoo - can be scaled to many manu server