Week 26

-

 Write a 1 - 2 paragraph journal post, of at least 250 words, of what you learned this week in CST 334.


    There was a lot to learn this week. Especially with all the lectures and readings assigned.  The first thing I learned about was CPU Scheduling Algorithms, intending to optimize turnaround time and response time. I learned about policies like FIFO, SJF, STCF, RR, and MLFQ. FIFO is a term I first learned in my Data Structures and Algorithms course, in which the first one in is the first one out. It is simple, but long jobs end up delaying short ones. Shortest job first is optimal for turnaround time, but requires knowing job lengths. Shortest time to completion first is better for dynamic arrivals, where we don't know what's coming next. Round robin is fair and slices response time, but worsens turnaround time. MLFQ uses priority queues and feedback to classify jobs. The rules include: Higher priority runs first, equal priority > Round Robin, new jobs start at highest priority, jobs using full time slice are demoted, then periodic priority boost to prevent starvation.

    I also learned about process management. Processes are running instances with a state and programs are static code on disks. I learned about fork(), creating a child process (a copy of the parent). exec() replaces process memory with a new program. and wait(), parent waits for child to exit.. Also about context switching, voluntary vs involuntary which we further discussed with our peers in our discussion. 

    We also went over formulas such as Turnaround Time (TAT): Completion Time - Arrival Time and Response Time (RT): First Run Time - Arrival Time. Where TAT includes full execution. RT measures initial delay.

Comments

Post a Comment

Popular posts from this blog

Week 11

-
 Summarize the feedback you received about your code     I received feedback that my variable names are clear and meaningful. My Code is functional but suboptimal, where logic adheres to the assignment but could use optimizations. I have an unused import which I already fixed in my final result. My code is clean and readable. And that my existing comments are concise and accurate but not exhaustive. Methods are documented but others lack explanations.       Identify any trends you noticed when evaluating the code of others A few logic errors here and there, as well as setting up the subclasses were a common theme. Was any part of the code a struggle for YOU?     I struggled a lot with the output statements, it is different than C++ and I would sometimes make too many arguments or too little, or silly little things like forgetting the %. toString was a pain to implement, as well as takeDamage. Was any part of writing the code easy for YOU? ...
Read more

Week 12

-
Work with some of your fellow classmates and go through your solution to project 1: LDPM Liam Connors What was your strategy for solving the assignments? My strategy for solving the assignments was to thoroughly read through the prompt, what each method asks, and then read the sample output to get an idea of how the program is supposed to run. Did you start writing code right away? Did you plan it out on paper?  After reading the prompt, I didn't plan anything on paper. I just started the assignment. What was THEIR strategy for solving the assignments? Liam's strategy for solving the assignment was to first match the UML diagram with fields/variables/methods. Thne he wrote TODOs for what he couldn't solve. He initially tried to create ac checklist document for the work but it became too overwhelming so he just worked on the assignment. Next time he would skip the understanding the entire assignment and instead spend his time focusing on individual methods to make sure they ...
Read more

Week 9

-
 I think my problem with solving Coding Bat challenges comes from the fact that I didn't know some Java lines like str.substring() and how to do -1 for the end of the string. I also need to think before I get to coding. Which is counterintuitive as I usually just code, then think about what went wrong. I sometimes took a break to solve these challenges. Like I stated previously, I threw code but now I know I should try and plan it better. These assignments took numerous attempts, it says 45 minutes for each assignment, but I probably spent ATLEAST double on both. I'm not as strong of a programmer as I'd like to be, it is a different language, but that shouldn't be an excuse. I will try hard to get good.
Read more