{"id":62,"date":"2019-08-05T16:28:45","date_gmt":"2019-08-05T16:28:45","guid":{"rendered":"http:\/\/redmine\/wordpress\/?page_id=62"},"modified":"2022-07-30T09:08:01","modified_gmt":"2022-07-30T09:08:01","slug":"metodisk-tilgang","status":"publish","type":"page","link":"https:\/\/www.berg-consult.dk\/en\/metodisk-tilgang","title":{"rendered":"Method"},"content":{"rendered":"
<\/div>
\n
\n

It must be realized that response time problems does not solve themselves.<\/p>\n\n\n\n

It may occur that problems disappear temporarily - just to reappear when the \"right\" circumstances return.<\/p>\n\n\n\n

Therefore it must be accepted that one or more changes are needed to solve the problems.<\/p>\n\n\n\n

The challenge is to identify the changes needed.<\/p>\n\n\n\n

This can be addressed in several ways - and some may be better approaches that others.<\/p>\n\n\n\n

Problems with response times can have many causes and it may seem overwelming where to begin. (see note on \"Large Organisations\" below).<\/p>\n\n\n\n

Large Organisations<\/strong>
A particular problem often arises, when the operational responsibility is distributed over more separate departments - like network, storage, server and application.<\/p>\n\n\n\n

In this type of organisation it is a reoccuring experience that attempts to solve problems with response time more or less degrades into a disjunct set of analyses each focusing on verifying whether a particular area has issues (examining ping-times, disk queues, run queue length etc.) with no focus on the experienced response time.<\/p>\n\n\n\n

This is more or less to be expected as a result of the usual rather narrow definition of area of responsibility associated with this type of distributed responsibility.<\/p>\n\n\n\n

Unfortunately such an approach does not really support finding the root cause(s) of a response time problem.<\/p>\n\n\n\n

Particulary in this situation it can be beneficial with an \"external view\" on the problems.<\/p>\n<\/div>\n\n\n\n

\n

My approach to address response time problems and problems with high resource consumption is in broad steps first to gather data - either already existing data or by measuring while reproducing the problem.<\/p>\n\n\n\n

Then analyse the data and determine the most appropriate action to take.<\/p>\n\n\n\n

The fundamental princip for the analysis is to \"follow the time\". <\/p>\n\n\n\n

This is based on the claim that (too long) response times are caused by spending too much time.<\/p>\n\n\n\n

It therefore seems reasonable that the analysis of response time should focus on identifying and quantifying where the time is spend.<\/p>\n\n\n\n

With this knowlegde it is rather straightforward to determine and prioritize the actions to take. <\/p>\n<\/div>\n<\/div><\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_themeisle_gutenberg_block_has_review":false,"footnotes":""},"class_list":["post-62","page","type-page","status-publish","hentry","entry"],"_links":{"self":[{"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/pages\/62","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/comments?post=62"}],"version-history":[{"count":1,"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/pages\/62\/revisions"}],"predecessor-version":[{"id":581,"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/pages\/62\/revisions\/581"}],"wp:attachment":[{"href":"https:\/\/www.berg-consult.dk\/en\/wp-json\/wp\/v2\/media?parent=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}