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

비밀번호

댓글 작성자
 




... 46  47  48  49  50  51  52  53  54  55  56  [57]  58  59  60  ...
NoWriterDateCnt.TitleFile(s)
12546정성태3/3/202118487개발 환경 구성: 545. github workflow/actions에서 빌드시 snk 파일 다루는 방법 - Encrypted secrets
12545정성태3/2/202121253.NET Framework: 1026. 닷넷 5에 추가된 POH (Pinned Object Heap) [10]
12544정성태2/26/202121601.NET Framework: 1025. C# - Control의 Invalidate, Update, Refresh 차이점 [2]
12543정성태2/26/202119284VS.NET IDE: 158. C# - 디자인 타임(design-time)과 런타임(runtime)의 코드 실행 구분
12542정성태2/20/202120926개발 환경 구성: 544. github repo의 Release 활성화 및 Actions를 이용한 자동화 방법 [1]
12541정성태2/18/202118455개발 환경 구성: 543. 애저듣보잡 - Github Workflow/Actions 소개
12540정성태2/17/202119892.NET Framework: 1024. C# - Win32 API에 대한 P/Invoke를 대신하는 Microsoft.Windows.CsWin32 패키지
12539정성태2/16/202119674Windows: 189. WM_TIMER의 동작 방식 개요파일 다운로드1
12538정성태2/15/202120238.NET Framework: 1023. C# - GC 힙이 아닌 Native 힙에 인스턴스 생성 - 0SuperComicLib.LowLevel 라이브러리 소개 [2]
12537정성태2/11/202120280.NET Framework: 1022. UI 요소의 접근은 반드시 그 UI를 만든 스레드에서! - 두 번째 이야기 [2]
12536정성태2/9/202119391개발 환경 구성: 542. BDP(Bandwidth-delay product)와 TCP Receive Window
12535정성태2/9/202118472개발 환경 구성: 541. Wireshark로 확인하는 LSO(Large Send Offload), RSC(Receive Segment Coalescing) 옵션
12534정성태2/8/202119206개발 환경 구성: 540. Wireshark + C/C++로 확인하는 TCP 연결에서의 closesocket 동작 [1]파일 다운로드1
12533정성태2/8/202117686개발 환경 구성: 539. Wireshark + C/C++로 확인하는 TCP 연결에서의 shutdown 동작파일 다운로드1
12532정성태2/6/202119485개발 환경 구성: 538. Wireshark + C#으로 확인하는 ReceiveBufferSize(SO_RCVBUF), SendBufferSize(SO_SNDBUF) [3]
12531정성태2/5/202117992개발 환경 구성: 537. Wireshark + C#으로 확인하는 PSH flag와 Nagle 알고리듬파일 다운로드1
12530정성태2/4/202121421개발 환경 구성: 536. Wireshark + C#으로 확인하는 TCP 통신의 Receive Window
12529정성태2/4/202119934개발 환경 구성: 535. Wireshark + C#으로 확인하는 TCP 통신의 MIN RTO [1]
12528정성태2/1/202119706개발 환경 구성: 534. Wireshark + C#으로 확인하는 TCP 통신의 MSS(Maximum Segment Size) - 윈도우 환경
12527정성태2/1/202119701개발 환경 구성: 533. Wireshark + C#으로 확인하는 TCP 통신의 MSS(Maximum Segment Size) - 리눅스 환경파일 다운로드1
12526정성태2/1/202116427개발 환경 구성: 532. Azure Devops의 파이프라인 빌드 시 snk 파일 다루는 방법 - Secure file
12525정성태2/1/202115292개발 환경 구성: 531. Azure Devops - 파이프라인 실행 시 빌드 이벤트를 생략하는 방법
12524정성태1/31/202115821개발 환경 구성: 530. 기존 github 프로젝트를 Azure Devops의 빌드 Pipeline에 연결하는 방법 [1]
12523정성태1/31/202117694개발 환경 구성: 529. 기존 github 프로젝트를 Azure Devops의 Board에 연결하는 방법
12522정성태1/31/202119907개발 환경 구성: 528. 오라클 클라우드의 리눅스 VM - 9000 MTU Jumbo Frame 테스트
12521정성태1/31/202118205개발 환경 구성: 527. 이더넷(Ethernet) 환경의 TCP 통신에서 MSS(Maximum Segment Size) 확인 [1]
... 46  47  48  49  50  51  52  53  54  55  56  [57]  58  59  60  ...