Differences
This shows you the differences between two versions of the page.
|
ep:labs:09 [2021/12/04 13:42] andrei.mirciu |
ep:labs:09 [2021/12/05 13:57] (current) andrei.mirciu [Tasks] |
||
|---|---|---|---|
| Line 28: | Line 28: | ||
| If Visual Studio prompts you with an "Expired" message, you will have to log in with your (university) account. | If Visual Studio prompts you with an "Expired" message, you will have to log in with your (university) account. | ||
| </note> | </note> | ||
| + | |||
| + | ===== Proof of Work ===== | ||
| + | |||
| + | Before you start, create a [[http://docs.google.com/|Google Doc]]. Here, you will add screenshots / code snippets / comments for each exercise. Whatever you decide to include, it must prove that you managed to solve the given task (so don't show just the output, but how you obtained it and what conclusion can be drawn from it). If you decide to complete the feedback for bonus points, include a screenshot with the form submission confirmation, but not with its contents. | ||
| + | |||
| + | When done, export the document as a //pdf// and upload in the appropriate assignment on Moodle. Remember, the cut-off time is 15 minutes after the lab ends. | ||
| ===== Contents ===== | ===== Contents ===== | ||
| Line 81: | Line 87: | ||
| Following the steps below, we can highlight how such a situation should be treated: | Following the steps below, we can highlight how such a situation should be treated: | ||
| - | ^ Part 1: Emphasize the CPU usage of a program ^^ | + | ^ Emphasize the CPU usage of a program ^^ |
| | **1.** Run, in parallel with the Windows Performance Recorder application, a program that generates CPU usage for a while and then stops. || | | **1.** Run, in parallel with the Windows Performance Recorder application, a program that generates CPU usage for a while and then stops. || | ||
| | **2.** Save the capture and open it in Windows Performance Analyzer. || | | **2.** Save the capture and open it in Windows Performance Analyzer. || | ||
| Line 93: | Line 99: | ||
| ==== 03. Network Monitoring ==== | ==== 03. Network Monitoring ==== | ||
| - | As you probably already know, the easiest and fastest way to monitor the amount of network traffic generated by a process can be done using Task Manager. | + | As you probably already know, the easiest and fastest way to monitor the amount of network traffic generated by a process on a Windows operating system is through using Task Manager. |
| - | == Windows Performance Recorder == | + | However, if the process generating the network activity is unknown, we can use Windows Performance Recorder, by selecting the **Networking I/O activity** profile. After we save the capture and open it in Windows Performance Analyzer, we will observe that the information offered is for the total use of the network, rather than per process statistics. |
| - | The resources for this tutorial include Winhttp.exe, a program that downloads putty.exe. The above screenshot displays its network activity. However, if the process generating the network activity is unknown, you can use Windows Performance Recorder with the following settings. Save and open the capture to view it. The statistics offered by Windows Performance Analyzer are for the total use of the network, rather than per process statistics. | + | |
| - | <spoiler> | + | Due to this reason, we are calling upon another tool developed by Microsoft, more precisely **[[https://www.microsoft.com/en-us/download/details.aspx?id=4865 | Microsoft Network Monitor]]**. After we install it, start it using “Run as administrator” and select the network interface through which the traffic is expected to pass (cable, wifi, etc.), we will be able to capture the frames. |
| - | {{ :ep:laboratoare:ep5_wpr-cpustart.jpg?400 |}} | + | |
| - | </spoiler> | + | Last but not least, another well-known tool that you should already be familiar with from the Linux network monitoring lab is **[[https://www.wireshark.org/download.html | Wireshark]]**. This can be used for displaying all traffic generated on a HTTP connection (it can also be HTTPS, as long as we control the server, but this is not in the scope of this tutorial). |
| + | |||
| + | <note tip> | ||
| + | When installing **Wireshark**, mare sure to select the **64-bit** version and accept the default settings. After that, you can start it and select the interface that you want to listen to. | ||
| + | </note> | ||
| ===== Tasks ===== | ===== Tasks ===== | ||
| <note warning> | <note warning> | ||
| - | The password for {{:ep:laboratoare:logs2.zip | log2.zip}} and {{:ep:labs:build.zip | build.zip}} is: //parola// | + | The skeleton for this lab can be found here: {{:ep:laboratoare:lab09-tasks.zip|}} |
| </note> | </note> | ||
| {{namespace>:ep:labs:09:contents:tasks&nofooter&noeditbutton}} | {{namespace>:ep:labs:09:contents:tasks&nofooter&noeditbutton}} | ||
