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  ...
12179정성태3/10/202064개발 환경 구성: 481. docker - PostgreSQL 컨테이너 실행
12178정성태3/10/202048개발 환경 구성: 480. Linux 운영체제의 docker를 위한 tcp 바인딩 추가
12177정성태3/9/202074개발 환경 구성: 479. docker - MySQL 컨테이너 실행
12176정성태3/9/202041개발 환경 구성: 478. 파일의 (sha256 등의) 해시 값(checksum) 확인하는 방법
12175정성태3/8/202096개발 환경 구성: 477. "Docker Desktop for Windows"의 "Linux Container" 모드를 위한 tcp 바인딩 추가
12174정성태3/8/2020125개발 환경 구성: 476. DockerDesktopVM의 파일 시스템 접근 [1]
12173정성태3/8/2020118개발 환경 구성: 475. docker - SQL Server 2019 컨테이너 실행 [1]
12172정성태3/8/202073개발 환경 구성: 474. docker - container에서 root 권한 명령어 실행(sudo)
12171정성태3/6/2020119VS.NET IDE: 143. Visual Studio - ASP.NET Core Web Application의 "Enable Docker Support" 옵션으로 달라지는 점
12170정성태3/6/202063오류 유형: 599. "Docker Desktop is switching..." 메시지와 DockerDesktopVM CPU 소비 현상
12169정성태3/5/2020119개발 환경 구성: 473. Windows nanoserver에 대한 docker pull의 태그 사용
12168정성태3/8/2020151개발 환경 구성: 472. 윈도우 환경에서의 dockerd.exe("Docker Engine" 서비스)가 Linux의 것과 다른 점
12167정성태3/5/202056개발 환경 구성: 471. C# - 닷넷 응용 프로그램에서 DB2 Express-C 데이터베이스 사용 (3) - ibmcom/db2express-c 컨테이너 사용
12166정성태3/14/202094개발 환경 구성: 470. Windows Server 컨테이너 - DockerMsftProvider 모듈을 이용한 docker 설치
12165정성태3/2/2020100.NET Framework: 900. 실행 시에 메서드 가로채기 - CLR Injection: Runtime Method Replacer 개선 - 세 번째 이야기(Monitor.Enter 후킹)파일 다운로드1
12164정성태2/29/202066오류 유형: 598. Surface Pro 6 - Windows Hello Face Software Device가 인식이 안 되는 문제
12163정성태2/27/2020132.NET Framework: 899. 익명 함수를 가리키는 delegate 필드에 대한 직렬화 문제
12162정성태2/28/2020140디버깅 기술: 166. C#에서 만든 COM 객체를 C/C++로 P/Invoke Interop 시 메모리 누수(Memory Leak) 발생파일 다운로드2
12161정성태2/26/202043오류 유형: 597. manifest - The value "x64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
12160정성태2/26/202082개발 환경 구성: 469. Reg-free COM 개체 사용을 위한 manifest 파일 생성 도구 - COMRegFreeManifest
12159정성태2/26/202046오류 유형: 596. Visual Studio - The project needs to include ATL support
12158정성태2/26/202093디버깅 기술: 165. C# - Marshal.GetIUnknownForObject/GetIDispatchForObject 사용 시 메모리 누수(Memory Leak) 발생파일 다운로드1
12157정성태2/27/2020102디버깅 기술: 164. C# - Marshal.GetNativeVariantForObject 사용 시 메모리 누수(Memory Leak) 발생 및 해결 방법파일 다운로드1
12156정성태2/25/202066오류 유형: 595. LINK : warning LNK4098: defaultlib 'nafxcw.lib' conflicts with use of other libs; use /NODEFAULTLIB:library
12155정성태2/25/202068오류 유형: 594. Warning NU1701 - This package may not be fully compatible with your project
12154정성태2/25/202065오류 유형: 593. warning LNK4070: /OUT:... directive in .EXP differs from output filename
1  [2]  3  4  5  6  7  8  9  10  11  12  13  14  15  ...