Microsoft MVP성태의 닷넷 이야기
글쓴 사람
첨부 파일

Jennifersoft provides a trial promotion on its APM solution such as JENNIFER, PHP, and .NET in 2019 and shares the examples of their application.

We are promoting JENNIFER .NET APM without charge.

As of September 2, Jennifersoft starts offering JENNIFER promotion for those who want to try the software including an application operator, a developer or even for community. On top of PHP, we expand the range of promotion by adding .NET platform. If you are interested in experiencing the JENNIFER, please feel free to apply and use it free of charge for 3 months.

Please click below link to apply:

JENNIFER Promotion 2019 Indonesia


You are allowed to install and operate the software without charge from September 2 to November 30, 2019. If you have experienced performance related issues, now is a good chance to find what caused the problem and reinvent it by installing JENNIFER .NET APM.

Let me give you an example of .NET APM that has just been installed.

The webpage indicated above is a B2C website selling fashion items in Korea. Normally, the webpage does not show any issues, however, it radically becomes slow ever since it exports a promotional event. For this reason, the webpage administrator installed the JENNIFER .NET.

As you can see from the below, the webpage continues to respond to requests without any issues.


When you look at the “X-View” indicated at lower right corner of the screen, there are myriad of dots. These dots are marked on the display time of X-axis once a request is completed. The Y-axis indicates the length of time to process such request. Most of the time, dots are marked within 1 to 2 seconds (1,000ms to 2,000ms). Based on my experience, I can assure you that the webpage is one of the well-made websites, considering the fact that it is made without a monitoring tool.

Unfortunately, the webpage has been suffering from disorder due to a promotional event like below.


When you look at the Y-axis on X-View, lots of dots are marked on an area beyond 8 seconds (8,000ms). In other words, the response time becomes very slow as the webpage takes more than 8 seconds to complete the related requests. When I select the area where the response time becomes slow like a figure below,

[Figure: JENNIFER-APM solution]

You can notice the time and the list of DB calling, and Web API calling that has occurred during the time of request. The figure indicates that it took tens of seconds at REST API calling for an outside company. Based on this result, the webpage company could come up with a solution to tackle the issue.

But the good thing is that this company was able to notice an error during the event period because the company at least conducted a basic system monitoring. Without the monitoring tool, the company could have not been noticed that they had a problem because the rapidly occurred requests by a push alarm normally end in such a short time. And it could have experienced decrease in sales and lost expense to prepare the promotion.

How do you feel now? Why don’t you find out yourself to see if you made your service reliably?

[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]

[최초 등록일: ]
[최종 수정일: 9/27/2019 ]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong,


댓글 쓴 사람

1  2  3  4  5  6  [7]  8  9  10  11  12  13  14  15  ...
12068정성태11/28/20191100디버깅 기술: 138. windbg와 Win32 API로 알아보는 Windows Heap 정보 분석 [2]파일 다운로드2
12067정성태11/27/2019738디버깅 기술: 137. 실제 사례를 통해 Debug Diagnostics 도구가 생성한 닷넷 웹 응용 프로그램의 성능 장애 보고서 설명 [1]파일 다운로드1
12066정성태11/27/2019529디버깅 기술: 136. windbg - C# PInvoke 호출 시 마샬링을 담당하는 함수 분석 - OracleCommand.ExecuteReader에서 OpsSql.Prepare2 PInvoke 호출 분석
12065정성태11/25/2019640디버깅 기술: 135. windbg - C# PInvoke 호출 시 마샬링을 담당하는 함수 분석파일 다운로드1
12064정성태11/25/2019890오류 유형: 580. HTTP Error 500.0/500.33 - ANCM In-Process Handler Load Failure
12063정성태11/21/2019677디버깅 기술: 134. windbg - RtlReportCriticalFailure로부터 parameters 정보 찾는 방법
12062정성태12/20/2019548디버깅 기술: 133. windbg - CoTaskMemFree/FreeCoTaskMem에서 발생한 덤프 분석 사례 - 두 번째 이야기
12061정성태11/20/2019618Windows: 165. CoTaskMemAlloc/CoTaskMemFree과 윈도우 Heap의 관계
12060정성태11/21/2019676디버깅 기술: 132. windbg/Visual Studio - HeapFree x64의 동작 분석
12059정성태11/20/2019642디버깅 기술: 131. windbg/Visual Studio - HeapFree x86의 동작 분석
12058정성태11/19/2019631디버깅 기술: 130. windbg - CoTaskMemFree/FreeCoTaskMem에서 발생한 덤프 분석 사례
12057정성태11/18/2019459오류 유형: 579. Visual Studio - Memory 창에서 유효한 주소 영역임에도 "Unable to evaluate the expression." 오류 출력
12056정성태11/18/2019800개발 환경 구성: 464. "Microsoft Visual Studio Installer Projects" 프로젝트로 EXE 서명 및 MSI 파일 서명 방법파일 다운로드1
12055정성태11/17/2019410개발 환경 구성: 463. Visual Studio의 Ctrl + Alt + M, 1 (Memory 1) 등의 단축키가 동작하지 않는 경우
12054정성태11/15/2019846.NET Framework: 869. C# - 일부러 GC Heap을 깨뜨려 GC 수행 시 비정상 종료시키는 예제
12053정성태11/15/2019506Windows: 164. 윈도우 10 - 명령행 창(cmd.exe) 속성에 (DotumChe, GulimChe, GungsuhChe 등의) 한글 폰트가 없는 경우
12052정성태11/15/2019439오류 유형: 578. Azure - 일정(schedule)에 등록한 runbook이 1년 후 실행이 안 되는 문제(Reason - The key used is expired.)
12051정성태12/2/2019942개발 환경 구성: 462. 시작하자마자 비정상 종료하는 프로세스의 메모리 덤프 - procdump [1]
12050정성태11/14/2019650Windows: 163. AcLayers의 API 후킹과 FaultTolerantHeap
12049정성태11/13/2019501.NET Framework: 868. (닷넷 프로세스를 대상으로) 디버거 방식이 아닌 CLR Profiler를 이용해 procdump.exe 기능 구현
12048정성태11/12/2019678Windows: 163. GUID 이름의 볼륨에 해당하는 파티션을 찾는 방법
12047정성태11/12/20191083Windows: 163. 안전하게 eject시킨 USB 장치를 물리적인 재연결 없이 다시 인식시키는 방법
12046정성태11/9/2019607오류 유형: 577. windbg - The call to LoadLibrary(...\sos.dll) failed, Win32 error 0n193
12045정성태10/27/2019509오류 유형: 576. mstest.exe 실행 시 "Visual Studio Enterprise is required to execute the test." 오류 - 두 번째 이야기
12044정성태10/27/2019613오류 유형: 575. mstest.exe - System.Resources.MissingSatelliteAssemblyException: The satellite assembly named "Microsoft.VisualStudio.ProductKeyDialog.resources.dll, ..."
12043정성태10/27/2019614오류 유형: 574. Windows 10 설치 시 오류 - 0xC1900101 - 0x4001E
1  2  3  4  5  6  [7]  8  9  10  11  12  13  14  15  ...