Mon premier blog

Troubleshooting with Wireshark: Locate the Source of Performance Problems Laura Chappell
Publisher: Protocol Analysis Institute, Inc.

Oct 17, 2010 - Having started out in the telecom industry (back when it was different from datacom – yes, I know, I'm old) I was always a fan of Fluke test gear, so I find it kind of amusing that they've decided to pick on OpenNMS to promote their latest commercial In this paragraph they state “Central polling misses performance from the user's perspective”. Apr 30, 2014 - In fact, most times it's a slow process as you eliminate one possibility after another until you find the root of the problem. Wireshark can help you diagnose network issues at a painfully detailed level. Whether you use Memcached or another caching technology, such as APC or Zend Server Cache, having an application level cache is important for performance & scalability. Aug 28, 2012 - Hand's on look at the HTTP Archive data format, which allows us to export, analyze, and visualize network performance data from the network timeline. Powered by Pylons and MongoDB under the hood, it allows Finding the root cause of a regression after the problem has occurred, and without the past performance data is often like groping in the dark. Another good thing to keep in mind about hard-to-diagnose problems: even if the viewer is the only thing being troublesome, that doesn't mean it's the source of the trouble. If this is greater than zero there may be performance issues when attempting to teleport. Using Curl, Wireshark and Charles, we can quickly and painlessly identify where the problem exists, without spending a lot of time making changes to our application to identify a problem. Feb 20, 2014 - Learn the pros and cons of normalisation techniques and find the right balance for your next project. We can do that too, with the help of another free and open-source tool: HAR Storage. We often use Wireshark in diagnosing customer issues, once OpenNMS determines the part of the network needing attention.