I couldn't find this documented elsewhere. Looking into the code:
There are two modes for CPU metrics reporting: the default one, and a "detailed CPU time" which can be enabled from the Setup screen (Display Options / Detailed CPU time). All of them show the percentage of time spent in different processes:
Blue: low priority processes (nice > ...
I suggest that you make the adjustments they have requested. Then benchmark the performance to show them that it made no difference. You could even go so far to benchmark it with LESS memory and vCPU to make your point.
Also, "We're paying you to support the software with actual solutions, not guesswork."
Providing you are confident you are within the given system specs they document.
Then any claim they are making in regards to requiring more RAM or CPU they should be able to back up. As the experts in their system I hold people to account on this.
Ask them specifics.
What information provided on the system indicates more RAM is needed and how did you ...
For a general sense of the scale of your problem netstat -s will track your total number of retransmissions.
# netstat -s | grep retransmitted
368644 segments retransmitted
You can aso grep for segments to get a more detailed view:
# netstat -s | grep segments
149840 segments received
150373 segments sent out
A colleague figured out how to achieve this. Instead of launching Performance Monitor directly:
Launch the Microsoft Management Console (mmc.exe)
File -> Add/Remove Snap-ins
Select Performance Monitor, select Add >, select OK.
Add your desired Counters as usual
File -> Save As...
The resulting .msc file will allow you to restore the Performance Monitor ...
iftop or pktstat -nT (for short term monitoring) is what you need to do this (under *nix). For long-term monitoring, ntop is useful.
Finding pktstat is a little tricky for those who aren't running a Debian / Ubuntu box, but this is a decent pktstat source-code archive
Use tcpview if you want the same kind of stats under windows
This is a good question because getting a read on memory issues for performance monitoring is difficult.
First off, when looking at Page Faults/sec keep in mind that this includes soft faults, hard faults and file cache faults. For the most part, you can ignore soft faults (i.e. paging between memory locations) and cache faults (reading files in to memory) ...
ISPs often prioritize traffic to speedtest.net so that they can brag how fast their connections are, while in reality, they don't provide that much bandwidth. They're perfectly aware that most users will only check that site for confirmation.
You also have to keep in mind that transfer speed relies both on the client and the server. In today's world most ...
Install sysstat package if you don't have it already and then use command sar -d 1. Watch the tps column. It gives you at least the ballpark figure.
But remember that actual maximum number of IOPS varies heavily depending on your server workload. A server with lots of sequential access might get more IOPS than a one doing lots of random access.
The big thing is to be able to prove that you are using best practices for your system allocation, notably RAM and CPU reservations for your SQL server.
All this being said the easiest thing is to make the adjustments requested, at least temporarily. If nothing else it tends to get vendors over feet dragging. I can't count the number of times I've needed ...
For this specific situation (where you have VMware and application developers or a third party who does not understand resource allocation), I use a week's worth of metrics obtained from vCenter Operations Manager (vCops - download a demo if needed) to pinpoint the real constraints, bottlenecks and sizing requirements of the application's VM(s).
A machine is idle when it's not performing the task it's supposed to perform for lack of requests. For example, if you had an email server, you could determine if it was fielding any requests from the email application on it. If it isn't, and that's the only thing on there, then it's idle. Things of course get more complicated with collocated services on a ...
Check out Apache's LogFormat directive. It allows to log the time taken to serve the request (%D and %T). This can be used for monitoring your server's response time. It will for example tell you if your server responds slower after you have made a change.
However, I am not aware of any tool which uses that information to create a report.
In addition to the other reasons posted, TCP connections don't work well with large files when the bandwidth-delay product becomes large.
Like on an otherwise fast connection to an island.
See Wikipedia's entry on TCP tuning.
So Speedtest can dump a small file through the connection at 95 mb/sec, but wget can only get 10 mb/sec on a 20 MB file.
Since you weren't using your memory for anything better, its being put to use as disk cache. If you start services, they will just take memory from the cache. This is a good thing, not a sign that anything is wrong. See linuxatemyram
You can do it with event handlers.
First, add an event handler for your Load average definition:
These stats are in /proc/net/netstat and collectl will monitor them for you either interactively or written to disk for later playback:
[root@poker ~]# collectl -st
waiting for 1 second sample...
#PureAcks HPAcks Loss FTrans
3 0 0 0
1 0 0 0
Of course, if you'd like to see ...
This is the way I use these words. Others may have additional or different usages. Depending on the job at hand, I will use the terms differently. Development teams and operations teams have different needs an usage.
Monitoring is monitoring. Usually it is ongoing, and preferably automated. Open source tools like Munin, Nagios, and MRTG fall into this ...
I used to work in support - and part of what you're asking sounds highly rational (and probably is): but there are a few questions to ask yourself prior to just doing the "performance enhancement" they're requesting
are you running at least at the vendor's stated minimum system requirements already?
if you're at least at minimum sysreqs, are you already at ...
The Process Queue Length count from the System performance counter object is:
Processor Queue Length is the number of threads in the processor queue[...]
This value is available in WMI via Win32_PerfFormattedData_PerfOS_System.
Open Performance Monitor (run as Admin) on your local workstation. Add counter, select counters from the hyper-v machine, Hyper-V Virtual IDE Controller or Hyper-V Virtual Storage Device, select counters and instances (VMs) as seems appropriate. You might have to fish around a bit to find the counter that makes the most sense to you.
There are some good ...
Here's what I did to get a process list snapshot directly in the notification emails, based on the idea by @quanta. It may contain paths specific to the way Nagios is installed on Debian/Ubuntu machines:
Created a wrapper script /usr/local/sbin/check_load that calls the original and appends the process snapshot if the exit code is 1 (WARNING) or 2 (...
New Relic says themselves that they use the .Net profiling API.
The .NET agent instruments application and system code using BCI (byte
code injection). This is done by registering the New Relic agent with
the CLR (Common Language Runtime) as a "profiler." The CLR calls out
Either ask to escalate the ticket or ask for a different rep. Depending on which vendor it is escalation may help if you say that you feel that the current level of support doesn't adequately address the issue. If they will not escalate then asking for a different rep may help because that requires much less "justification" since all it needs is to not be ...
By default Windows hide the entry because of a noted significant performance impact in collecting Disk metrics on a Server:
You need to register the Disk Perfcounter before you see this entry.
open a cmd.exe as admin
run diskperf -Y
close cmd.exe and run Taskmgr
Now you see the entry:
To analyze disk activity deeper, install the WPT, ...
Comparing the number of CPUs of a mainframe image isn't meaningful, most likely. Mainframes are designed to run multiple tasks at the same time, and give priority to whatever the business says is most important, and are capable of being very heavily virtualized, so looking at the number of CPUs doesn't tell you much. You have to understand the environment ...