Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 

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
; http://bit.ly/JenniferINAPromotion2019

PENDAFTARAN FREE TRIAL APM JENNIFER
; https://www.iorad.com/player/1594390/PENDAFTARAN-FREE-TRIAL-APM-JENNIFER#trysteps-1

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.

sample_net_mon_1.png

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.

sample_net_mon_2.png

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]
jennifer_main_features_5.png

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, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... [106]  107  108  109  110  111  112  113  114  115  116  117  118  119  120  ...
NoWriterDateCnt.TitleFile(s)
11274정성태8/22/201719331.NET Framework: 674. Thread 타입의 Suspend/Resume/Join 사용 관련 예외 처리
11273정성태8/22/201721624오류 유형: 415. 윈도우 업데이트 에러 Error 0x80070643
11272정성태8/21/201724750VS.NET IDE: 120. 비주얼 스튜디오 2017 버전 15.3.1 - C# 7.1 공개 [2]
11271정성태8/19/201719177VS.NET IDE: 119. Visual Studio 2017에서 .NET Core 2.0 프로젝트 환경 구성하는 방법
11270정성태8/17/201730642.NET Framework: 673. C#에서 enum을 boxing 없이 int로 변환하기 [2]
11269정성태8/17/201721435디버깅 기술: 93. windbg - 풀 덤프에서 .NET 스레드의 상태를 알아내는 방법
11268정성태8/14/201721013디버깅 기술: 92. windbg - C# Monitor Lock을 획득하고 있는 스레드 찾는 방법
11267정성태8/10/201725082.NET Framework: 672. 모노 개발 환경
11266정성태8/10/201724890.NET Framework: 671. C# 6.0 이상의 소스 코드를 Visual Studio 설치 없이 명령행에서 컴파일하는 방법
11265정성태8/10/201753128기타: 66. 도서: 시작하세요! C# 7.1 프로그래밍: 기본 문법부터 실전 예제까지 [11]
11264정성태8/9/201724020오류 유형: 414. UWP app을 signtool.exe로 서명 시 0x8007000b 오류 발생
11263정성태8/9/201719489오류 유형: 413. The C# project "..." is targeting ".NETFramework, Version=v4.0", which is not installed on this machine. [3]
11262정성태8/5/201718207오류 유형: 412. windbg - SOS does not support the current target architecture. [3]
11261정성태8/4/201720791디버깅 기술: 91. windbg - 풀 덤프 파일로부터 강력한 이름의 어셈블리 추출 후 사용하는 방법
11260정성태8/3/201718881.NET Framework: 670. C# - 실행 파일로부터 공개키를 추출하는 방법
11259정성태8/2/201718129.NET Framework: 669. 지연 서명된 어셈블리를 sn.exe -Vr 등록 없이 사용하는 방법
11258정성태8/1/201718900.NET Framework: 668. 지연 서명된 DLL과 서명된 DLL의 차이점파일 다운로드1
11257정성태7/31/201719131.NET Framework: 667. bypassTrustedAppStrongNames 옵션 설명파일 다운로드1
11256정성태7/25/201720601디버깅 기술: 90. windbg의 lm 명령으로 보이지 않는 .NET 4.0 ClassLibrary를 명시적으로 로드하는 방법 [1]
11255정성태7/18/201723170디버깅 기술: 89. Win32 Debug CRT Heap Internals의 0xBAADF00D 표시 재현 [1]파일 다운로드3
11254정성태7/17/201719493개발 환경 구성: 322. "Visual Studio Emulator for Android" 에뮬레이터를 "Android Studio"와 함께 쓰는 방법
11253정성태7/17/201719780Math: 21. "Coding the Matrix" 문제 2.5.1 풀이 [1]파일 다운로드1
11252정성태7/13/201718417오류 유형: 411. RTVS 또는 PTVS 실행 시 Could not load type 'Microsoft.VisualStudio.InteractiveWindow.Shell.IVsInteractiveWindowFactory2'
11251정성태7/13/201717078디버깅 기술: 88. windbg 분석 - webengine4.dll의 MgdExplicitFlush에서 발생한 System.AccessViolationException의 crash 문제 (2)
11250정성태7/13/201720664디버깅 기술: 87. windbg 분석 - webengine4.dll의 MgdExplicitFlush에서 발생한 System.AccessViolationException의 crash 문제 [1]
11249정성태7/12/201718470오류 유형: 410. LoadLibrary("[...].dll") failed - The specified procedure could not be found.
... [106]  107  108  109  110  111  112  113  114  115  116  117  118  119  120  ...