In this article we’ll discuss performance considerations for your storage subsystem. When selecting a storage solution you will usually consider the performance, which improves or degrades when considering multiple factors such as cost, reliability, availability and how easy it is to maintain and manage.
There are many factors to consider as storage requests work their way to the actual storage subsystem: cache-management, filesystem architecture, and volume management are all components involved in handling storage requests. They translate application calls into individual access requests, traversing the storage stack and creating a stream of commands that are presented to the disk storage subsystem. The sequence and quantity of those calls can improve or degrade the performance you get out of your storage subsystem. Read the full post
Incentive for raw commands
M3 (or its newer version which you should be using – M3v3) can do pretty much. However it can’t do anything.
M3 is good at timing execution of commands, apply simple parsing and upload the data to Monitis. Allowing you as the SysAdmin (and end-user of M3) to easily shape and design Custom Monitors for your system improving overall system uptime and stability.
Many times this is indeed what happens when trying to monitor different applications. The simple process of ‘Execution -> Parsing -> Reporting’ gets the job done. What happens when it doesn’t?
Well, I’ll tell you what happens – you are left a bit puzzled and think you’ll have to implement the Custom Monitors API which Monitis provide. True – until not long ago.
M3v3 bring you ‘Raw Commands’ capability in its last version. Read the full post
Category: Application Performance Management, Applications Monitoring, Articles, Database Monitoring, Linux Servers Monitoring, Monitis API, Monitis vs. Other services, Network Monitoring, Open Source, Performance Management, Sysadmin Tools, Uncategorized
In this article we’ll describe the Windows Azure monitor written in C#. Windows Azure has a set of different services, but we’ll limit our article to only those services that we use for capturing performance counters. If you’re new to Windows Azure and want more information you can visit the Microsoft Azure website.
Windows Azure Compute
There are three types of scalable compute instances which you can run in the cloud.
· Web Role – provide a dedicated Internet Information Services (IIS) web-server used for hosting front-end web applications.
· Worker Role – can run asynchronous, long-running or perpetual tasks independent of user interaction or input.
· VM Role – Virtual Machine (VM) roles, now in Beta, enable you to deploy a custom Windows Server 2008 R2 (Enterprise or Standard) image to Windows Azure. Read the full post