{"id":200,"date":"2009-02-01T17:45:20","date_gmt":"2009-02-01T17:45:20","guid":{"rendered":"http:\/\/blog.milamberspace.net\/?p=200"},"modified":"2009-07-11T22:05:39","modified_gmt":"2009-07-11T21:05:39","slug":"jmeter-suivre-un-tir-de-charge-en-mode-non-gui-avec-le-resume-statistique","status":"publish","type":"post","link":"https:\/\/blog.milamberspace.net\/index.php\/2009\/02\/01\/jmeter-suivre-un-tir-de-charge-en-mode-non-gui-avec-le-resume-statistique-200.html","title":{"rendered":"JMeter : suivre un tir de charge en mode non-gui avec le r\u00e9sum\u00e9 statistique"},"content":{"rendered":"<p style=\"\">Dans le <a href=\"http:\/\/blog.milamberspace.net\/index.php\/2009\/02\/01\/jmeter-pourquoi-executer-son-test-de-charges-en-mode-non-gui-sans-interface-graphique-192.html\">billet pr\u00e9c\u00e9dent<\/a>, j&rsquo;indiquais qu&rsquo;il est pr\u00e9f\u00e9rable de lancer un test de charge en utilisant JMeter en mode non-gui afin de pr\u00e9server les ressources de la machine JMeter.<\/p>\n<p style=\"\">Cependant en mode d&rsquo;ex\u00e9cution non-gui, il est frustrant de ne pas \u00ab voir ce qui se passe \u00bb : est-ce que le tir de charge se passe bien ?, est-ce qu&rsquo;il n&rsquo;y a pas d&rsquo;erreurs ?, y-a-t-il un blocage ?, &#8230;<\/p>\n<p style=\"\">Heureusement pour nous, JMeter a pr\u00e9vu une option qui va nous permettre d&rsquo;avoir quelques donn\u00e9es durant un tir de charges ex\u00e9cut\u00e9 en mode non-gui.<\/p>\n<p style=\"\">Il s&rsquo;agit du \u00ab summariser \u00bb, ce dernier va afficher \u00e0 intervalle pr\u00e9-d\u00e9fini les statistiques du test en cours.<!--more--> Voici un exemple :<\/p>\n<pre style=\"\">summary +   <span style=\"color: #ff6600;\">200 in  30.0s =    6.7\/s<\/span> <span style=\"color: #008000;\">Avg:    13 <\/span><span style=\"color: #3366ff;\">Min:     8<\/span> <span style=\"color: #993300;\">Max:    53<\/span> <span style=\"color: #ff0000;\">Err:     0 (0.00%)<\/span>\r\nsummary =  <span style=\"color: #ff6600;\">1448 in 225.0s =    6.4\/s<\/span> <span style=\"color: #008000;\">Avg:    13 <\/span><span style=\"color: #3366ff;\">Min:     6 <\/span><span style=\"color: #993300;\">Max:    67<\/span> <span style=\"color: #ff0000;\">Err:     0 (0.00%)<\/span><\/pre>\n<p style=\"\">La premi\u00e8re ligne indique que, depuis le dernier intervalle, il y a eu 200 \u00e9chantillons ex\u00e9cut\u00e9s durant les 30 derni\u00e8res secondes, ce qui fait un d\u00e9bit de 6,7 \u00e9chantillons par seconde. La moyenne des temps de r\u00e9ponses est  13 ms, le minimum durant la p\u00e9riode a \u00e9t\u00e9 8 ms, le maximum 53 ms. Et il n&rsquo;y a pas eu d&rsquo;erreur d\u00e9tect\u00e9es durant cette derni\u00e8re p\u00e9riode.<\/p>\n<p style=\"\">La deuxi\u00e8me ligne indique les m\u00eames donn\u00e9es, sauf que la p\u00e9riode correspond au temps depuis le (d\u00e9but) lancement du test de charge. Donc ici, c&rsquo;est 1448 \u00e9chantillons (tous confondus) en 225 secondes, etc.<\/p>\n<p style=\"\">Pour activer cette option, il faut aller simplement \u00e9diter le fichier<strong> JMETER_HOME\/bin\/jmeter.properties<\/strong> au niveau des param\u00e8tres suivants :<\/p>\n<pre style=\"\">#---------------------------------------------------------------------------\r\n# Summariser configuration (mainly applies to non-GUI mode)\r\n#---------------------------------------------------------------------------\r\n# Summariser settings\r\n#\r\n# Define the following property to automatically start a summariser with that name\r\n# (applies to non-GUI mode ony)\r\n#summariser.name=summary\r\n#\r\n# interval between summaries (in seconds) default 3 minutes\r\n#summariser.interval=180\r\n#\r\n# Write messages to log file\r\n#summariser.log=true\r\n#\r\n# Write messages to System.out\r\n#summariser.out=true<\/pre>\n<p style=\"\">Je vous recommande de faire un copier\/coller de ces \u00e9l\u00e9ments, puis les mettre dans le fichier <strong>user.properties<\/strong> (situ\u00e9 dans le m\u00eame r\u00e9pertoire), et les modifier \u00e0 votre convenance.<\/p>\n<p style=\"\">Par exemple :<\/p>\n<pre style=\"\">#---------------------------------------------------------------------------\r\n# Summariser configuration (mainly applies to non-GUI mode)\r\n#---------------------------------------------------------------------------\r\n# Summariser settings\r\n#\r\n# Define the following property to automatically start a summariser with that name\r\n# (applies to non-GUI mode ony)\r\n<span style=\"color: #0000ff;\">summariser.name=summary<\/span>\r\n#\r\n# interval between summaries (in seconds) default 3 minutes (180)\r\n<span style=\"color: #0000ff;\">summariser.interval=30<\/span>\r\n#\r\n# Write messages to log file <em>(c'est \u00e0 dire jmeter.log)<\/em>\r\n<span style=\"color: #0000ff;\">summariser.log=false<\/span>\r\n#\r\n# Write messages to System.out\r\n<span style=\"color: #0000ff;\">summariser.out=true<\/span><\/pre>\n<p style=\"\">Et voil\u00e0, c&rsquo;est pr\u00eat pour un affichage chaque 30 secondes sur la console durant le tir de charge.<\/p>\n<p style=\"\">Voici un exemple de sortie :<\/p>\n<pre style=\"\">milamber@surprise:~\/opt\/jakarta-jmeter-2.3.2\/bin$ jmeter -n -t .\/Simple.jmx -l .\/resultats.csv\r\nCreating summariser\r\nCreated the tree successfully using Simple.jmx\r\nStarting the test @ Sun Feb 01 08:45:44 WET 2009 (1233477944841)\r\nsummary +    49 in  15.0s =    3.3\/s Avg:    15 Min:     6 Max:    67 Err:     0 (0.00%)\r\nsummary +   199 in  30.0s =    6.6\/s Avg:    14 Min:     8 Max:    60 Err:     0 (0.00%)\r\nsummary =   248 in  45.0s =    5.5\/s Avg:    15 Min:     6 Max:    67 Err:     0 (0.00%)\r\nsummary +   200 in  30.0s =    6.7\/s Avg:    14 Min:     9 Max:    52 Err:     0 (0.00%)\r\nsummary =   448 in  75.0s =    6.0\/s Avg:    14 Min:     6 Max:    67 Err:     0 (0.00%)\r\n[......]\r\nsummary +   200 in  30.0s =    6.7\/s Avg:    12 Min:     8 Max:    51 Err:     0 (0.00%)\r\nsummary =  3848 in 585.0s =    6.6\/s Avg:    13 Min:     6 Max:   219 Err:     0 (0.00%)\r\nsummary +   152 in  30.1s =    5.0\/s Avg:    13 Min:     8 Max:    51 Err:     0 (0.00%)\r\nsummary =  4000 in 615.2s =    6.5\/s Avg:    13 Min:     6 Max:   219 Err:     0 (0.00%)\r\nsummary =  4000 in 615.2s =    6.5\/s Avg:    13 Min:     6 Max:   219 Err:     0 (0.00%)\r\nTidying up ...    @ Sun Feb 01 08:56:00 WET 2009 (1233478560189)\r\n... end of run<\/pre>\n<p style=\"\">Voil\u00e0, bon courage.<\/p>\n<p style=\"\">.\/<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Dans le billet pr\u00e9c\u00e9dent, j&rsquo;indiquais qu&rsquo;il est pr\u00e9f\u00e9rable de lancer un test de charge en utilisant JMeter en mode non-gui afin de pr\u00e9server les ressources de la machine JMeter. Cependant en mode d&rsquo;ex\u00e9cution non-gui, il est frustrant de ne pas \u00ab voir ce qui se passe \u00bb : est-ce que le tir de charge se &hellip; <a href=\"https:\/\/blog.milamberspace.net\/index.php\/2009\/02\/01\/jmeter-suivre-un-tir-de-charge-en-mode-non-gui-avec-le-resume-statistique-200.html\" class=\"more-link\">Continuer la lecture de <span class=\"screen-reader-text\">JMeter : suivre un tir de charge en mode non-gui avec le r\u00e9sum\u00e9 statistique<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32,33,34],"tags":[330,158,157,159],"class_list":["post-200","post","type-post","status-publish","format-standard","hentry","category-apache","category-jmeter","category-tests-de-charges","tag-jmeter","tag-non-gui","tag-summariser","tag-tir-de-charge"],"_links":{"self":[{"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/posts\/200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/comments?post=200"}],"version-history":[{"count":6,"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/posts\/200\/revisions"}],"predecessor-version":[{"id":204,"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/posts\/200\/revisions\/204"}],"wp:attachment":[{"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/media?parent=200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/categories?post=200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.milamberspace.net\/index.php\/wp-json\/wp\/v2\/tags?post=200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}